ScaffoldHub
  • Introduction
  • Modeling
  • Setup
    • NextJS
    • File Storage
    • Payments with Stripe
  • Debugging
  • End-to-end and Unit Tests
  • Deployment
    • Deploy to Vercel
  • Features
    • Projects
    • Preview
    • Tenants
    • Subscriptions and Payments
    • Security
    • File Storage
    • Authentication
      • Sign-in and Sign-up and Social Sign-in
      • Invitation
      • Password Reset
      • Password Change
      • Email Verification
    • Entity
      • Form
      • Filter and List
      • Export
      • Import
    • Audit Logs
    • Internationalization (I18n)
    • API Keys
    • API Documentation
  • Package.json
  • Support
  • Changelog
    • Documentation
    • Scaffolds
  • Custom Development
  • Legacy Scaffolds
  • Go to ScaffoldHub
Powered by GitBook
On this page
  1. Features

API Keys

PreviousInternationalization (I18n)NextAPI Documentation

Last updated 1 year ago

API keys are used when you need to call the API's directly.

You can define the permissions the API Key has access to via Scopes.

The scopes have only the permissions of the user's role.

After you create the API Key, the system will present the key for the calls. This key is only presented once after creation for security reasons.

So, if you are a read-only user, you can only give read-only access to your API Key. Read more about roles at .

Features > Security