Sign in / Sign up
API lifecycle Vehicle introduction

BETA features

Chargetrip regularly introduces new capabilities to help customers build better EV experiences. To ensure stability and gather feedback, all significant new features are introduced through the BETA program before becoming fully supported.

Guideline

If BETA features are used in an application, it is recommended communicating this to end customers through appropriate UI indicators or messaging. This helps set proper expectations about potential changes or limitations while the feature is being validated.

Types of BETA features

  • New operations: Entirely new queries, mutations, or subscriptions.
  • Extensions to existing operations: New optional input fields that add capabilities to existing operations.

What to expect from a BETA feature

  • Introduced as a non-breaking change

    • All BETA features are introduced as backward-compatible changes.

  • Clearly tagged in API schema and developer documentation

    • All BETA features are tagged with [BETA] in the GraphQL schema description.

  • Available to all

    • BETA features are accessible in the production API for every customer to test and explore.

  • Subject to change without deprecation process

    • The schema and underlying functionality of a BETA feature may change at any time without a formal deprecation notice.

  • Potentially unstable

    • BETA features haven't yet proven their reliability in production environments and may contain bugs or exhibit unexpected behavior. It's not recommended to use them for production-critical code.

From BETA to Stable

When a BETA feature is stable and its schema is final, it graduates to Stable.

This means:

  • The [BETA] tag is removed from the schema and developer documentation.
  • The feature is permanently integrated into the API.
  • It is now governed by Chargetrip's API lifecycle.

This transition is announced in the release notes.