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

Wagepoint Time Entries API

The Time Entries API from Wagepoint — 2 operation(s) for time entries.

Wagepoint Time Entries API is one of 7 APIs that Wagepoint publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Time Entries. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 4 operations across 2 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, /api.

4 operations 2 paths 10 schemas 1 GET2 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.wagepoint.com/api
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Wagepoint Time Entries API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

Paths & Operations 4

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

Time Entries 4
POST
/v1/companies/{company_id}/time-entries
Create time entries
CreateTimeEntries 2 params body → 201400401
GET
/v1/companies/{company_id}/time-entries
List time entries
ListTimeEntries 5 params → 200400422401
PATCH
/v1/companies/{company_id}/time-entries
Update time entries
UpdateTimeEntries 2 params body → 200
PATCH
/v1/companies/{company_id}/time-entries/status
Update time entry status
UpdateTimeEntryStatus 2 params body → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are problem_details (6 properties), time_entry_response (6 properties), create_time_entry_request (4 properties), update_time_entry_request (3 properties). Each schema is shown below with its type and property counts.

create_time_entry_request
object
4 properties
update_time_entries_response
object
1 property
list_items_response_time_entry_response
object
1 property
update_time_entries_request
object
1 property
time_entry_response
object
6 properties
update_time_entry_status_response
object
2 properties
problem_details
object
6 properties
create_time_entries_request
object
1 property
update_time_entry_request
object
3 properties
update_time_entry_status_request
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wagepoint-time-entries-api-openapi.yml Raw ↑

Other APIs Wagepoint publishes across the network.

Wagepoint Public API
Wagepoint Companies API
Wagepoint Health API
Wagepoint MCP API
Wagepoint Pay Groups API
Wagepoint Persons API
Where this information came from

This is an independent, third-party profile of Wagepoint Time Entries 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.