User authentication and session management for B2B integrations
Business Management (1.0.0)
Full-featured B2B API for business operations.
Base URL: https://api.alteg.io/api
V1 will be gradually deprecated. We recommend using V2 API for new integrations. V1 endpoints are maintained for backward compatibility, but new features will be released in V2 only.
Request
To add a field, the user must be part of the Chain associated with the location and have the appropriate access rights in the following section:
Settings → Access → Custom Fields → Create custom fields
- Mock serverhttps://developer.alteg.io/_mock/en/b2b-v1/openapi/custom_fields/{field_category}/{location_id}
- Productionhttps://api.alteg.io/api/v1/custom_fields/{field_category}/{location_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
'https://developer.alteg.io/_mock/en/b2b-v1/openapi/custom_fields/record/{location_id}' \
-H 'Accept: application/vnd.api.v2+json' \
-H 'Authorization: Bearer <YOUR_Bearer {PartnerToken}, User {UserToken}_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"type": "text",
"code": "my_text_field",
"title": "test field",
"user_can_edit": true,
"show_in_ui": true
}'{ "success": true, "data": { "id": 1, "salon_id": 1, "custom_field": { … } }, "meta": [] }
Request
To update a field, the user must be part of the Chain associated with the location and have the appropriate access rights in the following section
Settings → Access → Custom Fields → Modify custom fields
- Mock serverhttps://developer.alteg.io/_mock/en/b2b-v1/openapi/custom_fields/{field_category}/{location_id}/{field_id}
- Productionhttps://api.alteg.io/api/v1/custom_fields/{field_category}/{location_id}/{field_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
'https://developer.alteg.io/_mock/en/b2b-v1/openapi/custom_fields/record/{location_id}/{field_id}' \
-H 'Accept: application/vnd.api.v2+json' \
-H 'Authorization: Bearer <YOUR_Bearer {PartnerToken}, User {UserToken}_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"type": "text",
"code": "my_text_field",
"title": "test field",
"user_can_edit": true,
"show_in_ui": true
}'{ "success": true, "data": null, "meta": { "message": "Saved" } }
Request
To remove a field, the user must be part of the Chain associated with the location and have the appropriate access rights in the following section:
Settings → Access → Custom Fields → Remove custom fields
- Mock serverhttps://developer.alteg.io/_mock/en/b2b-v1/openapi/custom_fields/{field_category}/{location_id}/{field_id}
- Productionhttps://api.alteg.io/api/v1/custom_fields/{field_category}/{location_id}/{field_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X DELETE \
'https://developer.alteg.io/_mock/en/b2b-v1/openapi/custom_fields/record/{location_id}/{field_id}' \
-H 'Accept: application/vnd.api.v2+json' \
-H 'Authorization: Bearer <YOUR_Bearer {PartnerToken}, User {UserToken}_HERE>' \
-H 'Content-Type: string'{ "success": true, "data": null, "meta": { "message": "Deleted" } }