core-controller-endpoints

Configure Core API endpoints with Overwatch tokens and OrgIdentifier validation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jacobrocks1212/claude-config --skill core-controller-endpoints
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core-controller-endpoints
Source: https://github.com/jacobrocks1212/claude-config/tree/main/repos/cognito-forms/.claude/skills/core-controller-endpoints
Command: npx skills add https://github.com/jacobrocks1212/claude-config --skill core-controller-endpoints

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidance for securely creating, authenticating, and testing Core API endpoints used for administrative operations, data migrations, and support tooling in Cognito Forms, including the OrgIdentifier requirement, Overwatch token usage, and required headers.

Core Features & Use Cases

  • Inherit from BaseCoreController to define endpoints under /core/api/organization/{orgId}
  • Ensure the [OrgIdentifier] attribute is applied to the orgId parameter for authentication
  • Retrieve and apply an Overwatch token for Core API authentication
  • Enforce required headers such as X-Requested-By and Content-Length
  • Debug and troubleshoot common 401 scenarios across local and feature environments
  • Support safe migrations and tooling workflows with clear error handling and responses

Quick Start

Inherit from BaseCoreController, add [OrgIdentifier] to the orgId parameter, obtain an Overwatch token, and test the endpoint in the target environment.

Frequently Asked Questions about core-controller-endpoints

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate Core API endpoints for administrative operations?

Core API endpoints require an Overwatch token for authentication. You must inherit from BaseCoreController and apply the [OrgIdentifier] attribute to the orgId parameter to securely validate administrative operations under /core/api/.

Why does my Core API endpoint return a 401 error in local or feature environments?

A 401 error usually indicates missing or invalid Overwatch tokens, incorrect required headers like X-Requested-By, or environment misalignment. Troubleshoot by verifying token validity and ensuring all required headers are present.

What headers are required when testing Core API endpoints?

Required headers for Core API endpoints include X-Requested-By and Content-Length. Enforcing these headers alongside Overwatch token validation ensures consistent security and proper request handling during endpoint testing.

How do I set up Core API endpoints for safe data migrations?

Inherit from BaseCoreController to define endpoints under /core/api/organization/{orgId}. Apply the [OrgIdentifier] attribute for authentication and use clear error handling to support safe migrations and tooling workflows.

Can I use BaseCoreController for endpoint creation under /core/api/?

Yes, BaseCoreController is used to define endpoints under /core/api/organization/{orgId}. You must add the [OrgIdentifier] attribute to the orgId parameter and obtain an Overwatch token to test the endpoint in the target environment.

What is the OrgIdentifier requirement for Core API authentication?

The OrgIdentifier requirement mandates applying the [OrgIdentifier] attribute to the orgId parameter. This enforces secure authentication and validates the organization context for all Core API endpoint requests.