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

JOBOX.ai Users API

The users API from JOBOX.ai — 13 operation(s) for users.

JOBOX.ai Users API is one of 30 APIs that JOBOX.ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.

This API exposes 16 operations across 13 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.2.3(1S).

Requests are made against a single base URL, https://https://staging.jobox.ai/Kili.

16 operations 13 paths 2 schemas 11 GET2 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2.3(1S)
Base URL
https://api.jobox.ai/Kili
Resource Areas
1

Paths & Operations 16

Across 13 paths, the API surfaces 16 operations — 11 GET, 2 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

users 16
GET
/users/{user_id}/kyc_info
getInfo 2 params → default
POST
/users/{user_id}/kyc_info
submitInfo 2 params body → default
POST
/users
create_17 body → default
PUT
/usersdeprecated
updateDeprecated 1 param body → default
GET
/users/{user_id}/contacts
readContacts 1 param → default
GET
/users/{user_id}/contacts/all
readAllContacts 1 param → default
GET
/users/{user_id}/jobs/log/{start_time}/{end_time}
readJobsLog 4 params → default
GET
/users/{user_id}/jobs/log
readJobsLogByPage 2 params → default
GET
/users/{user_id}/jobs/{start_time}/{end_time}
readJobs 11 params → default
GET
/users/{user_id}/jobs
readJobsByPage 12 params → default
GET
/users/{user_id}/{contact_user_id}/jobs/{job_id}/status
sendStatus 4 params → default
GET
/users/{user_id}/{contact_user_id}/jobs/{job_id}/jobstatus
sendLatestJobStatus 4 params → default
GET
/users/{user_id}/usermasking
readActiveRulesForUser 2 params → default
GET
/users/{user_id}
read_16 2 params → default
PUT
/users/{user_id}
update_6 2 params body → default
PUT
/users/{user_id}/{verification_code}
verify 2 params → default

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are KycInfoDTO (19 properties), User (15 properties). Each schema is shown below with its type and property counts.

KycInfoDTO
object
19 properties
User
object
15 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jobox-ai-users-api-openapi.yml Raw ↑

Other APIs JOBOX.ai publishes across the network.

JOBOX.ai Applogic Users API
JOBOX.ai Bankinfo API
JOBOX.ai Commodities API
JOBOX.ai Contacts API
JOBOX.ai Dashboard API
JOBOX.ai Displayname API
JOBOX.ai Disputes API
JOBOX.ai External API
JOBOX.ai History API
JOBOX.ai Identification API
JOBOX.ai Joblog API
JOBOX.ai Joboxnumbers API
Where this information came from

This is an independent, third-party profile of JOBOX.ai Users 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.