> ## Documentation Index
> Fetch the complete documentation index at: https://help.skillsdb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Our Commitment to GraphQL Integrators

> The GraphQL API is not being deprecated — what the new REST API means for existing integrations

<Info>
  **Quick Summary:** If you are integrated with the SkillsDB GraphQL API today, nothing changes for you. The REST API is an addition, not a replacement, and you are not being asked to migrate.
</Info>

## The position, plainly

SkillsDB now offers two integration surfaces: this GraphQL API and a REST API with API-key authentication. The REST API exists because some customers asked for API keys and a conventional REST shape — **not** because GraphQL is going away.

* **No migration is required or planned.** Your existing GraphQL integration continues to work, on the same endpoint, with the same authentication.
* **No deprecation clock is running.** If that ever changes, you will hear it from us directly and in writing, with a generous timeline — not by discovering a notice in a changelog.
* **The GraphQL API continues to be maintained.** It is the same API our own application runs on, so it receives the same operational attention as the product itself.

## What has actually changed for GraphQL integrators

Two improvements, both in your favour:

1. **Schema introspection is now available to authenticated callers.** Previously the schema was not readable outside our own environments; now any authenticated request can run introspection — enabling schema discovery, client code generation, GraphQL IDE tooling, and visibility of `@deprecated` markers, which are GraphQL's in-band signal that a field is scheduled to change. Anonymous callers still cannot introspect.
2. **A breaking-change gate now guards the schema in CI.** A change that would remove or narrow anything you use cannot merge without an explicit, ticketed approval — the schema can no longer change out from under you as a side effect of a refactor.

## Choosing between the APIs

Use whichever fits. The REST API may suit new server-to-server integrations that prefer API keys, fixed resource shapes, and a published OpenAPI specification; GraphQL remains the right choice when you want to shape responses precisely. Both run against the same underlying system and the same permission model. Nothing about using one forecloses the other.