Work with this as data
Every API 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 apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/tithely:tithely-accounts-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Tithe.ly Accounts API
description: The Tithe.ly API lets churches and approved partners integrate with the Tithe.ly giving and church-technology platform.
version: '2.0'
contact:
name: Tithe.ly Support
url: https://docs.tithe.ly/reference/introduction
email: support@tithe.ly
servers:
- url: https://tithe.ly/api/v2
description: V2 REST API (live)
- url: https://tithe.ly/api/v1
description: V1 payments/tokenization API (live)
- url: https://tithelydev.com/api/v1
description: V1 payments/tokenization API (test/sandbox)
tags:
- name: Accounts
description: Authentication and login.
paths:
/login:
post:
operationId: login
tags:
- Accounts
summary: Authenticate a user
description: Authenticates a user and returns the credentials used to form the Authorization header for subsequent V2 requests. This is the only V2 endpoint that does not itself require the Authorization header.
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/LoginInput'
responses:
'200':
description: Authenticated. Returns API identity and token.
content:
application/json:
schema:
$ref: '#/components/schemas/LoginResult'
'401':
$ref: '#/components/responses/Unauthorized'
components:
schemas:
LoginInput:
type: object
required:
- email
- password
properties:
email:
type: string
format: email
password:
type: string
format: password
LoginResult:
type: object
description: Modeled. Returns the identity/token used to build the Authorization header.
properties:
api_id:
type: string
api_token:
type: string
user_id:
type: string
Error:
type: object
properties:
error:
type: string
message:
type: string
responses:
Unauthorized:
description: Missing or invalid API credentials.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
securitySchemes:
apiKeyAuth:
type: apiKey
in: header
name: Authorization
description: 'V2 requests use the header "Authorization: {API_ID}:{API_TOKEN}", where the ID and token come from the public/private API keys issued on access approval (and via the login endpoint). V1 payment calls use the private key issued on approval.'