Parse website screenshot

Parse

Parse is an open-source Backend-as-a-Service (BaaS). Originally the mobile backend company founded in 2011, backed by GV and DCVC, and acquired by Facebook in 2013 before the hosted parse.com service was shut down in 2017, Parse now lives on as the community-maintained Parse Platform. It centers on Parse Server, a self-hostable Node.js/Express backend, paired with first-party client SDKs for JavaScript, Apple (iOS/macOS), Android, Flutter/Dart, PHP, .NET, Swift and Arduino. Parse exposes a documented REST API over HTTP+JSON providing a schemaless object store, user authentication and sessions, roles and ACL/class-level permissions, file storage, rich queries, Cloud Code, Cloud Code Webhooks, LiveQuery real-time subscriptions, analytics and push notifications.

Parse publishes 1 API on the APIs.io network. Tagged areas include Company, Backend-as-a-Service, Mobile, Open-Source, and REST API.

The Parse catalog on APIs.io includes 1 event-driven AsyncAPI specification.

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

37.2/100 thin ▬ flat Agent 26/100 agent aware library Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
1 APIs
CompanyBackend-as-a-ServiceMobileOpen-SourceREST APIDatabaseAuthenticationPush NotificationsReal-Time

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
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/parse: 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 1

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

Parse REST API

HTTP+JSON REST API for the Parse Platform: object CRUD and queries, users and sessions, roles, files, analytics and push. Parse Server is self-hosted, so the base URL is the ope...

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Parse Webhooks

ASYNCAPI

Security Posture 3

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

Parse Authentication

apiKey · 5 schemes

SECURITY

Parse Domain Security

TLSv1.3 · DMARC

SECURITY

Parse Vulnerability Disclosure

contact published

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: parse
name: Parse
description: Parse is an open-source Backend-as-a-Service (BaaS). Originally the mobile backend company founded in 2011, backed
  by GV and DCVC, and acquired by Facebook in 2013 before the hosted parse.com service was shut down in 2017, Parse now lives
  on as the community-maintained Parse Platform. It centers on Parse Server, a self-hostable Node.js/Express backend, paired
  with first-party client SDKs for JavaScript, Apple (iOS/macOS), Android, Flutter/Dart, PHP, .NET, Swift and Arduino. Parse
  exposes a documented REST API over HTTP+JSON providing a schemaless object store, user authentication and sessions, roles
  and ACL/class-level permissions, file storage, rich queries, Cloud Code, Cloud Code Webhooks, LiveQuery real-time subscriptions,
  analytics and push notifications.
url: https://raw.githubusercontent.com/api-evangelist/parse/refs/heads/main/apis.yml
deliveryModel:
  model: library
  open_source: false
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - none
  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
  generated: '2026-09-03'
  method: derived
image: https://raw.githubusercontent.com/parse-community/parse-server/alpha/.github/parse-server-logo.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- dcvc
- gv
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Backend-as-a-Service
- Mobile
- Open-Source
- REST API
- Database
- Authentication
- Push Notifications
- Real-Time
tags_raw:
- Company
- Backend as a Service
- BaaS
- Mobile
- Open Source
- REST API
- Database
- Authentication
- Push Notifications
- Real Time
apis:
- name: Parse REST API
  description: 'HTTP+JSON REST API for the Parse Platform: object CRUD and queries, users and sessions, roles, files, analytics
    and push. Parse Server is self-hosted, so the base URL is the operator''s own Parse Server origin with the default /parse/
    mount.'
  humanURL: https://docs.parseplatform.org/rest/guide/
  baseURL: https://YOUR.PARSE-SERVER.HERE/parse/
  tags:
  - Backend-as-a-Service
  - REST API
  tags_raw:
  - Backend as a Service
  - REST API
  properties:
  - type: Documentation
    url: https://docs.parseplatform.org/rest/guide/
  - type: APIReference
    url: https://docs.parseplatform.org/rest/guide/#quick-reference
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: ParentCompany
  url: https://apis.io/providers/facebook/
  name: Facebook
  x-relationship: acquired
  x-evidence: Originally the mobile backend company founded in 2011, backed by GV and DCVC, and acquired by Facebook in 2013
    before the hosted parse.
- type: Website
  url: https://parseplatform.org
- type: DeveloperPortal
  url: https://docs.parseplatform.org/
- type: Documentation
  url: https://docs.parseplatform.org/
- type: APIReference
  url: https://docs.parseplatform.org/rest/guide/
- type: GettingStarted
  url: https://docs.parseplatform.org/parse-server/guide/
- type: GitHubOrganization
  url: https://github.com/parse-community
- type: Blog
  url: https://blog.parseplatform.org/
- type: Support
  url: https://community.parseplatform.org/
- type: Packages
  url: packages/parse-packages.yml
- type: SDKs
  url: packages/parse-packages.yml
- type: Authentication
  url: authentication/parse-authentication.yml
- type: Conventions
  url: conventions/parse-conventions.yml
- type: Idempotency
  url: conventions/parse-conventions.yml
- type: ErrorCatalog
  url: errors/parse-error-codes.yml
- type: Webhooks
  url: asyncapi/parse-webhooks.yml
- type: Lifecycle
  url: lifecycle/parse-lifecycle.yml
- type: Deprecation
  url: lifecycle/parse-lifecycle.yml
- type: ChangeLog
  url: changelog/parse-changelog.yml
- type: DataModel
  url: data-model/parse-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/parse-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/parse-llms.txt
- type: WellKnown
  url: well-known/parse-well-known.yml
- type: VulnerabilityDisclosure
  url: security/parse-vulnerability-disclosure.yml
- type: Security
  url: security/parse-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/parse-domain-security.yml
- type: Conformance
  url: conformance/parse-conformance.yml
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 14
  pass: local-v1

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/parse"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/parse/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/parse/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.

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