Papaya Global API Authentication

Toku connects to Papaya Global’s Workforce OS platform using API credentials that Papaya’s integration support team provisions specifically for the Toku connection. Credentials are issued per environment — no shared or personal logins are used.

Credentials

Papaya issues three values for each environment:

Credential	Purpose
API key	Identifies the Toku integration to Papaya’s API gateway
Client ID	Identifies the client application in the token exchange
Client secret	Proves the client’s identity — stored encrypted, never logged

Token Flow

Provision

Papaya integration support issues the API key, Client ID, and client secret for the Toku connection — one set per environment (sandbox and production).

Exchange

Toku’s backend exchanges the client credentials at Papaya’s token endpoint for a JWT access token.

Refresh

Access tokens are valid for 24 hours. Toku requests a fresh token automatically before expiry — the connection stays live without manual intervention.

# Token exchange (performed by Toku's backend)
# The exact token endpoint path is provisioned by Papaya per environment
curl -X POST "https://api.papayaglobal.com/<token_endpoint>/token" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "<toku_client_id>",
    "client_secret": "<toku_client_secret>"
  }'

Authenticated requests carry the JWT as a bearer header over HTTPS:

curl "https://api.papayaglobal.com/<resource>" \
  -H "Authorization: Bearer <access_token>"

Environments

Environment	Used for
Sandbox	Implementation testing with non-production data
Production	The live Toku connection

Each environment has its own credential set, so sandbox testing can never touch production payroll data. Credentials can be revoked by Papaya at any time, which immediately invalidates all tokens.

Papaya’s public developer documentation at docs.papayaglobal.com covers its Workforce Payments APIs. Worker and payroll data exchange for the Toku connection is arranged through Papaya’s Integration Center and provisioned with Papaya’s integration support during implementation.

Worker Sync

How Toku reads your worker roster

Payroll Sync

How Toku tracks payroll cycles and G2N data

⌘I

​Credentials

​Token Flow

​Environments

​Next

Worker Sync

Payroll Sync

Credentials

Token Flow

Environments

Next