How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bindbee Custom Fields API

The Custom Fields API from Bindbee — 7 operation(s) for custom fields.

Bindbee Custom Fields API is one of 55 APIs that Bindbee 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 12 operations across 7 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against the base URL https://api.bindbee.dev.

12 operations 7 paths 18 schemas 2 DELETE5 GET2 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.bindbee.dev
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Bindbee Custom Fields API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 12

Across 7 paths, the API surfaces 12 operations — 2 DELETE, 5 GET, 2 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Custom Fields 12
POST
/api/v1/custom-fields
Create Custom Field
create_custom_field_api_v1_custom_fields_post body → 201422401403429
GET
/api/v1/custom-fields
List Custom Fields
list_custom_fields_api_v1_custom_fields_get 5 params → 200422401403429
POST
/api/v1/custom-fields/mapping
Create Custom Field Mapping
create_custom_field_mapping_api_v1_custom_fields_mapping_post body → 201422401403429
GET
/api/v1/custom-fields/mapping
List Custom Field Mappings
list_custom_field_mappings_api_v1_custom_fields_mapping_get 2 params → 200422401403429
PATCH
/api/v1/custom-fields/mapping/{custom_field_mapping_id}
Update Custom Field Mapping
update_custom_field_mapping_api_v1_custom_fields_mapping__custom_field_mapping_id__patch 1 param body → 200422401403429404
DELETE
/api/v1/custom-fields/mapping/{custom_field_mapping_id}
Delete Custom Field Mapping
delete_custom_field_mapping_api_v1_custom_fields_mapping__custom_field_mapping_id__delete 1 param → 204422401403429404
GET
/api/v1/custom-fields/raw-data
Get Raw Data
get_raw_data_api_v1_custom_fields_raw_data_get 4 params → 200422401403429
POST
/api/v1/custom-fields/preview
Preview Custom Field
preview_custom_field_api_v1_custom_fields_preview_post body → 200422401403429
GET
/api/v1/custom-fields/configuration
Get Custom Fields Configuration
get_custom_fields_configuration_api_v1_custom_fields_configuration_get 3 params → 200422401403429
GET
/api/v1/custom-fields/{custom_field_id}
Get Custom Field
get_custom_field_api_v1_custom_fields__custom_field_id__get 1 param → 200422401403429404
PATCH
/api/v1/custom-fields/{custom_field_id}
Update Custom Field
update_custom_field_api_v1_custom_fields__custom_field_id__patch 1 param body → 200422401403429404
DELETE
/api/v1/custom-fields/{custom_field_id}
Delete Custom Field
delete_custom_field_api_v1_custom_fields__custom_field_id__delete 1 param → 204422401403429404

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are CustomFieldDetailExternal (10 properties), EffectiveCustomFieldEntry (8 properties), CustomFieldExternal (8 properties), CustomFieldMappingExternal (7 properties). Each schema is shown below with its type and property counts.

CustomFieldMappingUpdateExternal
object
1 property 1 required
CustomFieldCreateExternal
object
4 properties 3 required
CustomFieldMappingExternal
object
7 properties 4 required
PaginatedResponse_CustomFieldExternal_
object
3 properties 3 required
CustomFieldDetailExternal
object
10 properties 7 required
CustomFieldMappingCounts
object
3 properties 3 required
EffectiveCustomFieldResponse
object
5 properties 5 required
ErrorResponse
object
1 property 1 required
EffectiveCustomFieldEntry
object
8 properties 4 required
CustomFieldPreviewResponse
object
5 properties 4 required
CustomFieldMappingCreateExternal
object
4 properties 2 required
HTTPValidationError
object
1 property
CustomFieldSource
string
Category
string
CustomFieldExternal
object
8 properties 6 required
ValidationError
object
5 properties 3 required
CustomFieldUpdateExternal
object
4 properties
CustomFieldPreviewRequest
object
5 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Bindbee publishes across the network.

Bindbee Candidates API
Bindbee Departments API
Bindbee Employees API
Bindbee Jobs API
Bindbee Time Off API
Bindbee Activity API
Bindbee Application API
Bindbee Attachment API
Bindbee Bank Info API
Bindbee Benefit Coverages API
Bindbee Benefits API
Bindbee Candidate API
Where this information came from

This is an independent, third-party profile of Bindbee Custom Fields API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.