jsonapi

Validate API endpoints against the JSON:API v1.1 specification.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/vanhoangkha/cloud-security-audit --skill jsonapi-vanhoangkha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jsonapi
Source: https://github.com/vanhoangkha/cloud-security-audit/tree/main/multi-cloud/prowler/skills/jsonapi
Command: npx skills add https://github.com/vanhoangkha/cloud-security-audit --skill jsonapi-vanhoangkha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that your API endpoints strictly adhere to the JSON:API v1.1 specification, preventing common compliance errors and improving interoperability.

Core Features & Use Cases

  • Specification Validation: Enforces rules for document structure, resource objects, relationships, and error formatting.
  • HTTP Status Code Guidance: Provides correct HTTP status codes for various API operations.
  • Query Parameter Enforcement: Ensures proper handling of page, filter, sort, fields, and include parameters.
  • Use Case: When developing or reviewing a new API endpoint, use this skill to guarantee that all responses, including data structures, error messages, and relationship representations, conform to the JSON:API standard.

Quick Start

Validate that the API response for retrieving a user resource adheres to the JSON:API specification, paying close attention to the structure of the data object and any associated relationships.

Frequently Asked Questions about jsonapi

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

FAQPage Schema
How do I ensure my REST API responses are strictly compliant with the JSON:API v1.1 specification?

To ensure strict JSON:API v1.1 compliance, validate your API endpoints against rules for document structure, resource objects, relationships, and error objects. This prevents common compliance errors and improves overall interoperability.

What query parameters do I need to validate for JSON:API endpoint compliance?

JSON:API endpoint compliance requires validating query parameters including `page`, `filter`, `sort`, `fields`, and `include`. Proper handling of these parameters ensures correct pagination, filtering, sorting, field selection, and compound documents.

How do I validate the structure of resource objects and relationships in my JSON:API document?

Validating resource objects and relationships in a JSON:API document involves enforcing strict specification rules for the `data` object structure. This ensures that all associated relationships and resource representations conform to the v1.1 standard.

What HTTP status codes should I use for JSON:API operations?

JSON:API operations require correct HTTP status codes for various API actions. The specification provides guidance on the appropriate HTTP status codes to return for successful operations, errors, and validation failures.

When do I need to format error objects according to the JSON:API specification?

Error objects need formatting according to the JSON:API specification whenever your API endpoint returns an error. Enforcing strict error formatting rules ensures consistent error reporting and compliance with the v1.1 standard.