Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Remote Custom Fields API

The Custom Fields API from Remote — 3 operation(s) for custom fields.

Remote Custom Fields API is one of 101 APIs that Remote publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Custom Fields. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 3 paths, and defines 25 schemas. It is described by OpenAPI 3.0.0, at version 0.1.0.

Requests are made against 2 base URLs: https://gateway.remote.com/, https://gateway.remote-sandbox.com/.

6 operations 3 paths 25 schemas 3 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
0.1.0
Base URL
https://gateway.remote.com/v1/
Authentication
HTTP Basic, HTTP Bearer, HTTP Bearer, OAuth 2.0, OAuth 2.0, OAuth 2.0, OAuth 2.0
Resource Areas
1

Authentication & Security 7

Remote Custom Fields API declares 7 security schemes for authenticating requests. It accepts HTTP basic authentication (BasicAuth). It accepts HTTP bearer tokens (ClientToken). It accepts HTTP bearer tokens (CustomerAPIToken). It supports OAuth 2.0 (OAuth2) using the authorizationCode and clientCredentials flows, exposing 77 scopes. It supports OAuth 2.0 (OAuth2Assertion) using the clientCredentials flow, exposing 21 scopes. It supports OAuth 2.0 (OAuth2AuthorizationCode) using the authorizationCode flow, exposing 73 scopes. It supports OAuth 2.0 (OAuth2ClientCredentials) using the clientCredentials flow, exposing 18 scopes. By default, every request must be authenticated.

  • BasicAuth — Authenticate using the basic authentication for partners. Use the CLIENTID as login and CLIENTSECRET as password.
  • ClientToken — Authenticate a partner using only the the provided clienttoken. This authentication method only allows accessing marketing endpoints.
  • CustomerAPIToken — Authenticate using API Key generated by the customer in their Integration Settings page.
  • OAuth2 — Authenticate using OAuth 2.0 protocol.
  • OAuth2Assertion — Authenticate as the employee using the urn:ietf:params:oauth:grant-type:jwt-bearer grant in the OAuth2 protocol.
  • OAuth2AuthorizationCode — Authenticate as the token authorizer using authorizationcode / refreshtoken grants in the OAuth 2.0 protocol.
  • OAuth2ClientCredentials — Authenticate using clientcredentials grant in the OAuth 2.0 protocol.

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 3 GET, 1 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Custom Fields 6
GET
/v1/custom-fields
Lists custom fields definitions
get_v1_custom-fields 2 params → 200401404422
POST
/v1/custom-fields
Create Custom Field Definition
post_v1_custom-fields body → 200401404422
GET
/v1/employments/{employment_id}/custom-fields
List custom field value for an employment
get_v1_employments_employment_id_custom-fields 3 params → 200401404422
GET
/v1/custom-fields/{custom_field_id}/values/{employment_id}
Show a custom field value
get_v1_custom-fields_custom_field_id_values_employment_id 2 params → 200401404422
PATCH
/v1/custom-fields/{custom_field_id}/values/{employment_id}
Update a Custom Field Value
patch_v1_custom-fields_custom_field_id_values_employment_id (2) 2 params body → 200401403404422
PUT
/v1/custom-fields/{custom_field_id}/values/{employment_id}
Update a Custom Field Value
patch_v1_custom-fields_custom_field_id_values_employment_id 2 params body → 200401403404422

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are EmploymentCustomField (7 properties), CreateSingleSelectCustomFieldDefinitionParams (6 properties), CreateCurrencyCustomFieldDefinitionParams (6 properties), CreateGeneralCustomFieldDefinitionParams (5 properties). Each schema is shown below with its type and property counts.

CreateSingleSelectCustomFieldDefinitionParams
object
Schema for creating a single select custom field definition
6 properties 6 required
ParameterError
object
3 properties 3 required
ListEmploymentCustomFieldsResponse
object
Response schema listing many customfields
1 property
SingleSelectMetadata
object
The metadata for a single select custom field
1 property 1 required
ListEmploymentCustomFieldValuePaginatedResponse
object
Response schema listing many customfieldvalues
1 property
EmploymentCustomFieldValueResponse
object
Response containing a single custom field value for an employment.
1 property 1 required
UnauthorizedResponse
object
Returned when the request does not include valid authentication credentials. Ensure you are passing a valid OAuth2 access token or API token in the Authorizati…
1 property 1 required
UnprocessableEntityResponse
object
CurrencyCode
string
Currency code of the SWIFT fee. Only present when processingfee is set.
CreateCurrencyCustomFieldDefinitionParams
object
Schema for creating a currency custom field definition
6 properties 6 required
CustomFieldDataType
string
The datatype of the custom field
ListEmploymentCustomFieldValueResponse
object
A custom field value as returned in list responses, including the field definition details alongside the value.
4 properties 4 required
ActionError
object
3 properties 3 required
EmploymentCustomFieldValue
object
The value of a custom field for a specific employment. The type of value depends on the custom field's data type.
2 properties 2 required
CustomFieldSimpleDataType
string
The datatype of the custom field
UpdateEmploymentCustomFieldValueParams
object
Schema for updating a custom field value.
1 property 1 required
ForbiddenResponse
object
Returned when the authenticated user or token does not have permission to perform the requested action. Check that the token has the required OAuth2 scopes and…
1 property 1 required
NotFoundResponse
object
Returned when the requested resource does not exist or is not accessible with the current authentication credentials.
1 property
CustomFieldVisibilityScope
string
Who can see this custom field and its values. Controls visibility across different user roles.
EmploymentCustomField
object
A custom field definition that can be applied to employments within a company. Custom fields allow you to store additional structured data on employments beyon…
7 properties 7 required
CustomFieldDataEntryAccess
string
Who can enter or edit values for this custom field. Controls which users see the field as editable vs read-only.
CreateCustomFieldDefinitionParams
Schema for creating a custom field definition
EmploymentCustomFieldValueJsonValue
object
The value for a single-select custom field, containing both the option ID and its human-readable label.
2 properties 2 required
CreateEmploymentCustomFieldResponse
object
Response returned after successfully creating a new custom field definition.
1 property 1 required
CreateGeneralCustomFieldDefinitionParams
object
Schema for creating a general custom field definition
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

remote-custom-fields-api-openapi.yml Raw ↑

Other APIs Remote publishes across the network.

Remote Address Details API
Remote Administrative Details API
Remote Background Checks API
Remote Bank Account Details API
Remote Basic Information API
Remote Benefit Offers API
Remote Benefit Offers By Employment API
Remote Benefit Renewals API
Remote Benefits API
Remote Billing Address Details API
Remote Billing API
Remote Billing Documents API