NameSuffix Endpoints
Last updated
Was this helpful?
Last updated
Was this helpful?
This document explains the methods you may use to work with the NameSuffix endpoints in the Federated Authority Document database.
The full JSON-LD NameSuffix object is defined at .
Getting a list of NameSuffix objects from the Federated Authority Document Database is accomplished by querying the endpoint using a REST GET. Optional parameters may be provided to filter and paginate the result.
Getting a list of NameSuffix object from the Federated Authority Document Database is accomplished by querying the endpoint using a REST GET with no optional parameters.
Provides a list of all NameSuffix objects.
Pagination is provided for the list where count is the total quantity of objects in the data-set, limit is how many objects are returned in the current list, and offset is the first object in the set from that offset point. This is configurable in the request, but the default is a limit of 50 objects starting from offset 0.
In the below example, with a limit of 2, page 1 starts from offset 0 with two values (
limit). Page 2 starts fromoffset= 2. Page 3 fromoffset= 4, etc. There would be 5 pages to display the data - two objects at a time. This is illustrative only, and the actual local pages will depend on your limit and count.
These are the parameters you can optionally supply to the filter. These fields work as a logical AND.
Field
Description
abbreviation
Searches by abbreviation.
suffix
Searches by suffix.
sort_dir
0 = descending, 1 = ascending
search
Searches across all searchable fields.
limit
Combined with offset, provides pagination by limiting results.
offset
Combined with limit, provides pagination by shifting the first record.
When posting an object, all ID fields are ignored and can be set to null. Any parameter (key) or sub-object not provided is considered skipped and the value will come back null.
A local_reference_id may be supplied to any core object or sub-object which will be echoed within the object response. This allows tagging of any object to ensure accurate processing is maintained in some systems. (See the local_reference_id section for more detail.)
All new objects require a person id performing the update which is accomplished via the x-requester-person header value.
When you send a POST to create an object, you must supply an x-requester-person in the header as the person id making the request. This sets the created_by field in the audit record to the person who added the object.
Only suffix and abbreviation are required to create a NameSuffix object, however you may supply any other data that complies with the full schema.
The response object that is returned is the FULL NameSuffix JSON object as defined by grcschema.
Some properties cannot be changed and are ignored. (e.g. id)
A local_reference_id may be supplied to any core object or sub-object which will be echoed within the object response. This allows tagging of any object to ensure accurate processing required by some systems. (See the local_reference_id section for more detail.)
When you send a PATCH to modify an object, you must supply an x-requester-person in the header as the person id making the request. This sets the modified_by field in the audit record to the person who modified the object.
local_reference_idFor POST and PATCH operations, you may send an optional local_reference_id for the core object and any sub-objects in unordered lists (@set arrays). This local_reference_id will be returned (like an echo) for that object.
It is recommended you use a Type 4 UUID which is unique for that object in your system and tie the federated ID to your record for later use in querying the federated system for that object.
For the core object, you may place a
local_reference_idat the object root level, and it will be returned in the response.
SEND
RESPONSE
For the core object, you may place a
local_reference_idat the object root level, and it will be returned in the response. Do not addlocal_reference_idto the container objects like CoreMetaData.
SEND & RESPONSE
Getting a filtered list of NameSuffix objects from the Federated Authority Document Database is accomplished by querying the endpoint using a REST GET with url parameters.
Getting a single NameSuffix object from the Federated Authority Document Database is accomplished by querying the endpoint using a REST GET.
Adding a new NameSuffix object is accomplished by sending an application/json content type object to the endpoint as a REST POST.
The full JSON-LD object is defined at , and the endpoint will accept the the entire object for processing. This includes array items (@set).
Updating a NameSuffix object is accomplished by sending an application/json content type object to the endpoint as a REST PATCH.
The full JSON-LD object is defined at , and the endpoint will accept an existing NameSuffix object (with applicable changes) for processing.
Change the properties of the object pulled from GET /NameSuffix/:id by sending an application/json PATCH to the endpoint and the full NameSuffix object will be returned with the requested changes.