Skip to main content
A template’s keys come in three kinds. Core keys are a vocabulary Vumasign publishes: people, South African ID and passport, contact details, addresses, employment, employers and banking. Map your data to them once and every template named with them is addressed the same way. Organisation keys are every other key your own templates use, in the naming grammar (namespace.attribute, see Naming fields). Legacy keys are any other spelling a template still carries from before; they work as addresses and are names to replace.

Reading it

GET /api/v1/vocabulary answers with both lists, for a key holding templates:read, test or live. It carries an ETag, and If-None-Match answers with no body while nothing has changed.
  • core is version 1.0.0, 50 keys, with the subject keys the core standardises: spouse, dependant_<n>, beneficiary_<n>, witness_<n>, where n counts from one.
  • organisation lists the keys your organisation’s live templates use and the core does not: each key’s type (a field type, or choice for a question), how many templates use it, up to 5 labels printed beside the boxes that carry it, and for a question the option values in use. It is derived from your templates whenever you read it, archived templates left out, and it never lists another organisation’s keys.

How the core changes

The core uses semantic versioning. A minor version adds keys, options or synonyms. A key or an option value is never renamed or removed; at most it is deprecated, with the key that replaces it. A template named with a core key never needs renaming because the core moved.

Using a core key

  • person.*, the two address namespaces and employment.* describe a person. With subject null they are the form’s principal person, the one the signer answers for; with subject set to spouse, the spouse’s. employer.* and bank.* describe the organisation and take no subject.
  • A key in a core namespace (person, employer, employment, residential_address, postal_address, bank) must be a core key: a key such as person.sa_idnumber is refused with the core key it most likely means.
  • A choice key is a question (or a dropdown), and its options are fixed: a question named with person.gender offers male, female, and its boxes take those option values.
  • A core key is refused on a field of a kind it does not describe: a date key on a tickbox, or a choice key on a text box.

The keys

person.*

Subject-capable: with subject null it is the form’s principal person; with a subject, that person’s.

residential_address.*

Subject-capable: with subject null it is the form’s principal person; with a subject, that person’s.

postal_address.*

Subject-capable: with subject null it is the form’s principal person; with a subject, that person’s.

employment.*

Subject-capable: with subject null it is the form’s principal person; with a subject, that person’s.

employer.*

Not subject-capable: it describes the organisation, and a subject is refused.

bank.*

Not subject-capable: it describes the organisation, and a subject is refused.