DailyPay

DailyPay is an on-demand pay (earned wage access) platform that lets employees access wages they have already earned before the scheduled payday. The company sells to employers across healthcare, retail, restaurants, manufacturing, hospitality and the public sector, and integrates with 180+ HCM, payroll and time-management systems. Its developer surface — the DailyPay REST API — is a json:api-shaped OAuth 2.0 / OpenID Connect API covering people, jobs, organizations, paychecks, accounts (including the EARNINGS_BALANCE account that carries available earnings), transfers and PCI-scoped debit-card tokenization, complemented by DailyPay Elements, a set of hosted drop-in iframe components for embedding on-demand pay into partner applications.

DailyPay publishes 8 APIs on the APIs.io network, including Accounts API, Card Tokenization API, Health API, and 5 more. Tagged areas include Company, Payments, Payroll, Human Resources, and Earned Wage Access.

DailyPay’s developer surface includes documentation, API reference, getting-started guide, authentication, support, engineering blog, signup flow, and 35 more developer resources.

🌐 Visit website 📡 Source on GitHub

57.3/100 strong ▬ flat Agent 51/100 agent native saas Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0

AccessSelf serve

1 APIs 1 MCP Servers

Company Payments Payroll Human Resources Earned Wage Access On-Demand Pay Financial-Services Fintech Money Transfer Benefits

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Payments & Card Management

BC-1340

Transfers

POST /rest/transfers

Human Capital Management

BC-300

Paychecks

GET /rest/paychecks/{paycheck_id} GET /rest/paychecks

Kin Score

Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0

Composite quality — 57.3/100 · strong

Contract Quality 10.4 / 19

Developer Ergonomics 11.0 / 15

Access Clarity 7.5 / 15

Operational Transparency 2.8 / 10

Contract Governance 1.6 / 9

Discoverability 5.7 / 8

Regulatory Posture 10.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 51/100 · agent native

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/dailypay: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 8

Individual APIs this provider publishes, each with its own machine-readable definition.

DailyPay Accounts API

The _accounts_ endpoint provides comprehensive information about money accounts. You can retrieve account details, including the account's unique ID, a link to the account holde...

DailyPay Card Tokenization API

Securely tokenize personal cards for use in the accounts API.

DailyPay Health API

The _health_ endpoint provides a simple health check for the API. **Functionality:** Check the status of the API to ensure it is functioning correctly.

DailyPay Jobs API

The _jobs_ endpoint provides access to comprehensive information about a person's employment. It enables you to retrieve details about individual jobs, including information abo...

DailyPay Organizations API

The _organizations_ endpoint provides details about a business entity, such as an employer, or a group of people, such as a division. The response includes the organization name...

DailyPay Paychecks API

The _paychecks_ endpoint provides detailed information about paychecks. You can retrieve individual paycheck details, including the person and job associated with the paycheck, ...

DailyPay People API

The _people_ endpoint allows you to see information related to who owns resources such as jobs and accounts. **Functionality:** Retrieve limited details about a person, includin...

DailyPay Transfers API

The _transfers_ endpoint allows you to initiate and track money movement. You can access transfer details, including the transfer's unique ID, amount, currency, status, schedule...

Scroll for all 8

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

DailyPay MCP Server

MCP SERVER

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Dailypay Authentication

oauth2/openIdConnect · 2 schemes

SECURITY

Dailypay Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Dailypay Vulnerability Disclosure

Hackerone · security.txt

SECURITY

Dailypay Trust Center

SOC 2, ISO 27001, PCI DSS

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Dailypay Scopes

5 scopes · clientCredentials/authorizationCode

5 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Dailypay Agentic Access

18 operations · 6 acting

AGENTIC

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

WellKnown

MCPServer

LLMsTxt

AgenticAccess

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Lifecycle

Conventions

Idempotency

ErrorCatalog

DataModel

Conformance

Components

Scroll for all 7

Build 5

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

DeclineCodes

ToolCrosswalk

Access & Security 7

Authentication, authorization, and security posture

Authentication

OAuthScopes

Compliance

TrustCenter

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Scroll for all 7

Operate 3

Status, limits, changes, and where to get help

Support

Support

HelpCenter

HelpCenter

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

OpenIDConnect

OpenIDConnect

Source (apis.yml)

aid: dailypay
name: DailyPay
description: DailyPay is an on-demand pay (earned wage access) platform that lets employees access wages they have already
  earned before the scheduled payday. The company sells to employers across healthcare, retail, restaurants, manufacturing,
  hospitality and the public sector, and integrates with 180+ HCM, payroll and time-management systems. Its developer surface
  — the DailyPay REST API — is a json:api-shaped OAuth 2.0 / OpenID Connect API covering people, jobs, organizations, paychecks,
  accounts (including the EARNINGS_BALANCE account that carries available earnings), transfers and PCI-scoped debit-card tokenization,
  complemented by DailyPay Elements, a set of hosted drop-in iframe components for embedding on-demand pay into partner applications.
url: https://raw.githubusercontent.com/api-evangelist/dailypay/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - security
  - sandbox
  generated: '2026-09-02'
  method: derived
image: https://developer.dailypay.com/static/svgs/dp_text.svg
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pipeline
specificationVersion: '0.23'
created: '2026-08-01'
modified: '2026-08-01'
x-enrichment:
  date: '2026-08-01'
  status: enriched
  artifacts_added: 30
  pass: local-v1
tags:
- Company
- Payments
- Payroll
- Human Resources
- Earned Wage Access
- On-Demand Pay
- Financial-Services
- Fintech
- Money Transfer
- Benefits
tags_raw:
- Company
- Payments
- Payroll
- Human Resources
- Earned Wage Access
- On-Demand Pay
- Financial Services
- Fintech
- Money Transfer
- Benefits
apis:
- aid: dailypay:dailypay-accounts-api
  name: DailyPay Accounts API
  description: 'The _accounts_ endpoint provides comprehensive information about money

    accounts. You can retrieve account details, including the

    account''s unique ID, a link to the account holder, type, subtype,

    verification status, balance details, transfer capabilities, and

    user-specific information such as names, routing numbers, and partial

    account numbers.



    **Functionality:** Access detailed user account information, verify

    account balances, view transfer capabilities, and access user-specific

    details associated with each account.'
  humanURL: https://developer.dailypay.com/products/rest/reference
  baseURL: https://api.dailypay.com/rest
  tags:
  - Account
  tags_raw:
  - Accounts
  properties:
  - type: OpenAPI
    url: openapi/dailypay-accounts-api-openapi.yml
  - type: Documentation
    url: https://developer.dailypay.com/products/rest
  - type: APIReference
    url: https://developer.dailypay.com/products/rest/reference
- aid: dailypay:dailypay-card-tokenization-api
  name: DailyPay Card Tokenization API
  description: Securely tokenize personal cards for use in the accounts API.
  humanURL: https://developer.dailypay.com/products/rest/reference
  baseURL: https://api.dailypay.com/rest
  tags:
  - Card Tokenization
  properties:
  - type: OpenAPI
    url: openapi/dailypay-card-tokenization-api-openapi.yml
  - type: Documentation
    url: https://developer.dailypay.com/products/rest
  - type: APIReference
    url: https://developer.dailypay.com/products/rest/reference
- aid: dailypay:dailypay-health-api
  name: DailyPay Health API
  description: "The _health_ endpoint provides a simple health check for the API. \n\n**Functionality:** Check the status\
    \ of the API to ensure it is functioning\ncorrectly."
  humanURL: https://developer.dailypay.com/products/rest/reference
  baseURL: https://api.dailypay.com/rest
  tags:
  - Health
  properties:
  - type: OpenAPI
    url: openapi/dailypay-health-api-openapi.yml
  - type: Documentation
    url: https://developer.dailypay.com/products/rest
  - type: APIReference
    url: https://developer.dailypay.com/products/rest/reference
- aid: dailypay:dailypay-jobs-api
  name: DailyPay Jobs API
  description: "The _jobs_ endpoint provides access to comprehensive information \nabout a person's employment. It enables\
    \ you to retrieve details about\nindividual jobs, including information about the organization\nthey work for, status,\
    \ wage rate, job title, location,\npaycheck settings, and related links to associated accounts."
  humanURL: https://developer.dailypay.com/products/rest/reference
  baseURL: https://api.dailypay.com/rest
  tags:
  - Job
  tags_raw:
  - Jobs
  properties:
  - type: OpenAPI
    url: openapi/dailypay-jobs-api-openapi.yml
  - type: Documentation
    url: https://developer.dailypay.com/products/rest
  - type: APIReference
    url: https://developer.dailypay.com/products/rest/reference
- aid: dailypay:dailypay-organizations-api
  name: DailyPay Organizations API
  description: "The _organizations_ endpoint provides details about a business entity, \nsuch as an employer, or a group of\
    \ people, such as a division.\n\nThe response includes the organization name and ID which can be used to\nmake subsequent\
    \ endpoint calls related to the organization and its\nemployees."
  humanURL: https://developer.dailypay.com/products/rest/reference
  baseURL: https://api.dailypay.com/rest
  tags:
  - Organization
  tags_raw:
  - Organizations
  properties:
  - type: OpenAPI
    url: openapi/dailypay-organizations-api-openapi.yml
  - type: Documentation
    url: https://developer.dailypay.com/products/rest
  - type: APIReference
    url: https://developer.dailypay.com/products/rest/reference
- aid: dailypay:dailypay-paychecks-api
  name: DailyPay Paychecks API
  description: "The _paychecks_ endpoint provides detailed information about paychecks. \nYou can retrieve individual paycheck\
    \ details, including the\nperson and job associated with the paycheck, its status, pay period,\nexpected deposit date,\
    \ total debited amount, withholdings, earnings, and\ncurrency.\n\n**Functionality:** Retrieve specific paycheck details,\
    \ including payee and\njob information, and monitor the status and financial details of each\npaycheck."
  humanURL: https://developer.dailypay.com/products/rest/reference
  baseURL: https://api.dailypay.com/rest
  tags:
  - Paychecks
  properties:
  - type: OpenAPI
    url: openapi/dailypay-paychecks-api-openapi.yml
  - type: Documentation
    url: https://developer.dailypay.com/products/rest
  - type: APIReference
    url: https://developer.dailypay.com/products/rest/reference
- aid: dailypay:dailypay-people-api
  name: DailyPay People API
  description: "The _people_ endpoint allows you to see information related to who owns \nresources such as jobs and accounts.\n\
    \n**Functionality:** Retrieve limited details about a person, including\ntheir name, global status, and state of residence."
  humanURL: https://developer.dailypay.com/products/rest/reference
  baseURL: https://api.dailypay.com/rest
  tags:
  - People
  properties:
  - type: OpenAPI
    url: openapi/dailypay-people-api-openapi.yml
  - type: Documentation
    url: https://developer.dailypay.com/products/rest
  - type: APIReference
    url: https://developer.dailypay.com/products/rest/reference
- aid: dailypay:dailypay-transfers-api
  name: DailyPay Transfers API
  description: 'The _transfers_ endpoint allows you to initiate and track money movement.  You can access transfer details,
    including the transfer''s unique ID, amount, currency, status, schedule, submission and resolution times, fees, and related
    links to the involved parties.


    **Functionality** Retrieve transfer information, monitor transfer statuses, view transfer schedules, and access relevant
    links for the source, destination, and origin of the transfer.


    **Important** - Account origin: a user initiated movement of money from one account to another - Paycheck origin: an automatic
    (system-generated) movement of money as part of payroll'
  humanURL: https://developer.dailypay.com/products/rest/reference
  baseURL: https://api.dailypay.com/rest
  tags:
  - Transfers
  properties:
  - type: OpenAPI
    url: openapi/dailypay-transfers-api-openapi.yml
  - type: Documentation
    url: https://developer.dailypay.com/products/rest
  - type: APIReference
    url: https://developer.dailypay.com/products/rest/reference
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/dailypay-capability-edges.yml
  name: DailyPay Business Capability Map
- type: Overlay
  url: overlays/dailypay-rest-overlay.yaml
- type: Website
  url: https://www.dailypay.com/
- type: DeveloperPortal
  url: https://developer.dailypay.com/
- type: Documentation
  url: https://developer.dailypay.com/products/rest
- type: APIReference
  url: https://developer.dailypay.com/products/rest/reference
- type: GettingStarted
  url: https://developer.dailypay.com/products/rest/guides/auth
- type: Authentication
  url: authentication/dailypay-authentication.yml
- type: OAuthScopes
  url: scopes/dailypay-scopes.yml
- type: OpenIDConnect
  url: https://auth.dailypay.com/.well-known/openid-configuration
- type: Support
  url: https://www.dailypay.com/contact/
- type: HelpCenter
  url: https://www.dailypay.com/help/
- type: Blog
  url: https://www.dailypay.com/resource-center/blog/
- type: BlogRSS
  url: https://www.dailypay.com/resource-center/blog/feed/
- type: GitHubOrganization
  url: https://github.com/dailypay
- type: SignUp
  url: https://dailypay.app.link/vYyj0iSlyTb
- type: Login
  url: https://account.dailypay.com/
- type: TermsOfService
  url: https://www.dailypay.com/en-us/legal/terms-of-service/
- type: PrivacyPolicy
  url: https://www.dailypay.com/en-us/legal/privacy/
- type: Compliance
  url: https://www.dailypay.com/en-us/legal/compliance/
- type: TrustCenter
  url: security/dailypay-trust-center.yml
- type: Security
  url: https://www.dailypay.com/security/vulnerability-disclosure-program/
- type: VulnerabilityDisclosure
  url: security/dailypay-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/dailypay-domain-security.yml
- type: StatusPage
  url: https://status.dailypay.com/
- type: Lifecycle
  url: lifecycle/dailypay-lifecycle.yml
- type: Packages
  url: packages/dailypay-packages.yml
- type: SDKs
  url: packages/dailypay-packages.yml
- type: Conventions
  url: conventions/dailypay-conventions.yml
- type: Idempotency
  url: conventions/dailypay-conventions.yml
- type: ErrorCatalog
  url: errors/dailypay-problem-types.yml
- type: DeclineCodes
  url: errors/dailypay-decline-codes.yml
- type: DataModel
  url: data-model/dailypay-data-model.yml
- type: Conformance
  url: conformance/dailypay-conformance.yml
- type: Sandbox
  url: sandbox/dailypay-sandbox.yml
- type: Components
  url: components/dailypay-components.yml
- type: WellKnown
  url: well-known/dailypay-well-known.yml
- type: MCPServer
  url: mcp/dailypay-mcp.yml
- type: ToolCrosswalk
  url: mcp/dailypay-tool-crosswalk.yml
- type: LLMsTxt
  url: llms/dailypay-llms.txt
- type: AgenticAccess
  url: agentic-access/dailypay-agentic-access.yml
- type: AgentSkill
  url: skills/_index.yml

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/dailypay"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/dailypay/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/dailypay/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.