Button

Button (usebutton.com) is a mobile commerce technology company whose platform connects Publishers and Brands in a two-sided marketplace: publishers deep-link their users into retailer apps and sites with full attribution, and brands acquire and re-engage customers through those optimized journeys. Its server-to-server APIs cover personalized Offers, attributed Link and Shortlink generation (including Amazon creator links), Brand partnership details, Billing/affiliation transaction reporting, and Order reporting, complemented by Publisher SDKs, Merchant Libraries, and HMAC-signed transaction webhooks.

Button publishes 7 API contracts indexed on the APIs.io network, including Accounts API, Brands Api, Create API, and 4 more. Tagged areas include Commerce, Mobile Commerce, Affiliates, Attribution, and Deep Linking.

The Button catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Button’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, changelog, authentication, and 31 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

52.2/100 developing ▬ flat Agent 29/100 agent ready Front door AI 3/6 light Heartbeat 83/100 alive saas Full breakdown ↓
scored 2026-11-02 · rubric v0.26.0 · Show this score on your site →

5 published contracts 3 Agent Skills

Commerce Mobile Commerce Affiliates Attribution Deep Linking Offers Publishers Retail

What this lets a business do 1

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

Product Telemetry & Experimentation Management

BC-4280

CreateLinks Api

POST /create POST /

Kin Score

Kin Score How this is scored →
scored 2026-11-02 · rubric v0.26.0

Composite quality — 52.2/100 · developing

Contract Quality 10.7 / 19

Developer Ergonomics 8.3 / 15

Access Clarity 6.5 / 15

Operational Transparency 4.4 / 10

Contract Governance 1.6 / 9

Discoverability 5.9 / 8

Regulatory Posture 5.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 29/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 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 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) 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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/usebutton/"><img src="https://apis.io/badge/usebutton/card.svg" alt="Button on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 43.4 — up to +11.3 composite points
Contract Quality scores 57.1 — up to +10.7 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/usebutton/apis.yml: open an issue on github.com/api-evangelist/usebutton to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Mobile SDK Publishers (Play SDK Index, CocoaPods, ADA certification)	mixed	40.0	-	-
Amazon Seller Ecosystem (Selling Partner Appstore, Amazon Ads partners)	mixed	40.0	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 7

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

Button Order API

Brands report new orders, order updates (including partial returns), and cancellations to Button server-to-server, passing the Button Attribution Token (btn_ref) captured by the...

Button Accounts API

The Accounts API from Button — 2 operation(s) for accounts.

Button Brands Api

The Brands Api API from Button — 1 operation(s) for brands api.

Button Create API

The Create API from Button — 2 operation(s) for create.

Button Links Api

The Links Api API from Button — 1 operation(s) for links api.

Button Offers API

The Offers API from Button — 1 operation(s) for offers.

Button Transactions API

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Button API Rules

49 rules · 45 errors 1 warnings 3 info

SPECTRAL

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

Usebutton Authentication

http · 1 scheme

SECURITY

Usebutton Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Usebutton Vulnerability Disclosure

Hackerone · contact published

SECURITY

Usebutton Trust Center

SOC 2, GDPR

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 6

Authentication, authorization, and security posture

Authentication

Compliance

Security

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 4

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: usebutton
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-02'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/usebutton.png
name: Button
description: 'Button (usebutton.com) is a mobile commerce technology company whose platform connects Publishers and Brands
  in a two-sided marketplace: publishers deep-link their users into retailer apps and sites with full attribution, and brands
  acquire and re-engage customers through those optimized journeys. Its server-to-server APIs cover personalized Offers, attributed
  Link and Shortlink generation (including Amazon creator links), Brand partnership details, Billing/affiliation transaction
  reporting, and Order reporting, complemented by Publisher SDKs, Merchant Libraries, and HMAC-signed transaction webhooks.'
url: https://raw.githubusercontent.com/api-evangelist/usebutton/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- norwest-venture-partners
- slow-ventures
x-tier: stub
x-tier-reason: portfolio-lead
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 30
  pass: local-v1
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-09-16'
tags:
- Commerce
- Mobile Commerce
- Affiliates
- Attribution
- Deep Linking
- Offers
- Publishers
- Retail
tags_raw:
- Commerce
- Mobile Commerce
- Affiliate
- Attribution
- Deep Linking
- Offers
- Publishers
- Retail
apis:
- name: Button Order API
  description: Brands report new orders, order updates (including partial returns), and cancellations to Button server-to-server,
    passing the Button Attribution Token (btn_ref) captured by the Merchant Library; documented in the guides with create
    (POST /v1/order), update (POST /v1/order/{order_id}), and cancel (DELETE /v1/order/{order_id}).
  humanURL: https://developer.usebutton.com/docs/order-api-overview
  baseURL: https://api.usebutton.com/v1/order
  tags:
  - Order
  - Brands
  tags_raw:
  - Orders
  - Brands
  properties:
  - type: Documentation
    url: https://developer.usebutton.com/docs/order-api-overview
- aid: usebutton:usebutton-accounts-api
  name: Button Accounts API
  description: The Accounts API from Button — 2 operation(s) for accounts.
  humanURL: https://developer.usebutton.com/reference/list-brand-details
  baseURL: https://api.usebutton.com/v1/brands
  tags:
  - Account
  tags_raw:
  - Accounts
  properties:
  - type: OpenAPI
    url: openapi/usebutton-accounts-api-openapi.yml
  - type: Documentation
    url: https://developer.usebutton.com/reference/list-brand-details
  - type: Documentation
    url: https://developer.usebutton.com/reference/billing-api-introduction
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-link-2
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-brand-shortlink
  - type: Documentation
    url: https://developer.usebutton.com/docs/getting-button-content
- aid: usebutton:usebutton-brands-api-api
  name: Button Brands Api
  description: The Brands Api API from Button — 1 operation(s) for brands api.
  humanURL: https://developer.usebutton.com/reference/list-brand-details
  baseURL: https://api.usebutton.com/v1/brands
  tags:
  - Brands Api
  properties:
  - type: OpenAPI
    url: openapi/usebutton-brands-api-api-openapi.yml
  - type: Documentation
    url: https://developer.usebutton.com/reference/list-brand-details
  - type: Documentation
    url: https://developer.usebutton.com/reference/billing-api-introduction
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-link-2
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-brand-shortlink
  - type: Documentation
    url: https://developer.usebutton.com/docs/getting-button-content
- aid: usebutton:usebutton-create-api
  name: Button Create API
  description: The Create API from Button — 2 operation(s) for create.
  humanURL: https://developer.usebutton.com/reference/list-brand-details
  baseURL: https://api.usebutton.com/v1/brands
  tags: []
  tags_raw:
  - Create
  properties:
  - type: OpenAPI
    url: openapi/usebutton-create-api-openapi.yml
  - type: Documentation
    url: https://developer.usebutton.com/reference/list-brand-details
  - type: Documentation
    url: https://developer.usebutton.com/reference/billing-api-introduction
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-link-2
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-brand-shortlink
  - type: Documentation
    url: https://developer.usebutton.com/docs/getting-button-content
- aid: usebutton:usebutton-links-api-api
  name: Button Links Api
  description: The Links Api API from Button — 1 operation(s) for links api.
  humanURL: https://developer.usebutton.com/reference/list-brand-details
  baseURL: https://api.usebutton.com/v1/brands
  tags:
  - Links Api
  properties:
  - type: OpenAPI
    url: openapi/usebutton-links-api-api-openapi.yml
  - type: Documentation
    url: https://developer.usebutton.com/reference/list-brand-details
  - type: Documentation
    url: https://developer.usebutton.com/reference/billing-api-introduction
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-link-2
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-brand-shortlink
  - type: Documentation
    url: https://developer.usebutton.com/docs/getting-button-content
- aid: usebutton:usebutton-offers-api
  name: Button Offers API
  description: The Offers API from Button — 1 operation(s) for offers.
  humanURL: https://developer.usebutton.com/reference/list-brand-details
  baseURL: https://api.usebutton.com/v1/brands
  tags:
  - Offers
  properties:
  - type: OpenAPI
    url: openapi/usebutton-offers-api-openapi.yml
  - type: Documentation
    url: https://developer.usebutton.com/reference/list-brand-details
  - type: Documentation
    url: https://developer.usebutton.com/reference/billing-api-introduction
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-link-2
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-brand-shortlink
  - type: Documentation
    url: https://developer.usebutton.com/docs/getting-button-content
- aid: usebutton:usebutton-transactions-api
  name: Button Transactions API
  description: The Transactions API from Button — 1 operation(s) for transactions.
  humanURL: https://developer.usebutton.com/reference/list-brand-details
  baseURL: https://api.usebutton.com/v1/brands
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/usebutton-transactions-api-openapi.yml
  - type: Documentation
    url: https://developer.usebutton.com/reference/list-brand-details
  - type: Documentation
    url: https://developer.usebutton.com/reference/billing-api-introduction
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-link-2
  - type: Documentation
    url: https://developer.usebutton.com/reference/generate-a-brand-shortlink
  - type: Documentation
    url: https://developer.usebutton.com/docs/getting-button-content
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/usebutton-capability-edges.yml
  name: Button Business Capability Map
- type: Overlay
  url: overlays/usebutton-billing-overlay.yaml
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/button/overview
- type: Website
  url: https://usebutton.com
- type: DeveloperPortal
  url: https://developer.usebutton.com
- type: Documentation
  url: https://developer.usebutton.com/docs
- type: APIReference
  url: https://developer.usebutton.com/reference
- type: GettingStarted
  url: https://developer.usebutton.com/reference/getting-started
- type: Support
  url: https://www.usebutton.com/contact-us
- type: Blog
  url: https://www.usebutton.com/blog
- type: GitHubOrganization
  url: https://github.com/button
- type: Login
  url: https://app.usebutton.com/account/login
- type: TermsOfService
  url: https://www.usebutton.com/support/terms-of-service
- type: PrivacyPolicy
  url: https://www.usebutton.com/support/privacy-policy
- type: StatusPage
  url: https://status.usebutton.com
- type: ChangeLog
  url: changelog/usebutton-changelog.yml
- type: ChangeLog
  url: https://developer.usebutton.com/changelog
- type: Lifecycle
  url: lifecycle/usebutton-lifecycle.yml
- type: Authentication
  url: authentication/usebutton-authentication.yml
- type: Conventions
  url: conventions/usebutton-conventions.yml
- type: ErrorCatalog
  url: errors/usebutton-problem-types.yml
- type: Webhooks
  url: asyncapi/usebutton-webhooks.yml
- type: Sandbox
  url: sandbox/usebutton-sandbox.yml
- type: Packages
  url: packages/usebutton-packages.yml
- type: SDKs
  url: packages/usebutton-packages.yml
- type: X-MCPServerCandidate
  url: mcp/usebutton-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/usebutton-llms.txt
- type: WellKnown
  url: well-known/usebutton-well-known.yml
- type: Conformance
  url: conformance/usebutton-conformance.yml
- type: Compliance
  url: https://www.usebutton.com/support/security
- type: Security
  url: https://www.usebutton.com/support/security
- type: DataModel
  url: data-model/usebutton-data-model.yml
- type: AgentSkill
  name: Fetch offers and generate an attributed link
  url: skills/usebutton-offers-to-link.md
- type: AgentSkill
  name: Reconcile commissions with the Billing API
  url: skills/usebutton-billing-reconciliation.md
- type: AgentSkill
  name: Create attributed creator shortlinks
  url: skills/usebutton-creator-shortlinks.md
- type: TrustCenter
  url: security/usebutton-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/usebutton-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/usebutton-domain-security.yml

Button API — frequently asked questions

Does Button have an API?

Yes. APIs.io lists 7 APIs from Button, including Button Order API, Button Accounts API and Button Brands Api, and 4 more.

Is there an OpenAPI specification for the Button API?

Yes. APIs.io indexes 6 OpenAPI specifications for Button, each linked for download from this page.

How do I authenticate with the Button API?

Button uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Usebutton Authentication.

Is the Button API ready for AI agents?

Button has a Kin Score of 52.2 out of 100 (developing) and an Agent Readiness score of 28.7 (agent-ready), scored by API Evangelist on 2026-11-02.

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/usebutton"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/usebutton/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.