How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Acceptance Criteria

Acceptance Criteria User Stories API

The User Stories API from Acceptance Criteria — 2 operation(s) for user stories.

Documentation Provider Profile APIs.io OpenAPI GitHub

This API exposes 4 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.example.com/v1.

4 operations 2 paths 6 schemas 2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.github.com
Authentication
HTTP Bearer
Contact
API Evangelist
License
Creative Commons Attribution 4.0
Resource Areas
1

Authentication & Security 1

Acceptance Criteria User Stories API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

User Stories 4
GET
/stories
List user stories
listUserStories 3 params → 200401500
POST
/stories
Create a user story
createUserStory body → 201400401500
GET
/stories/{storyId}
Get a user story
getUserStory 1 param → 200401404500
PUT
/stories/{storyId}
Update a user story
updateUserStory 1 param body → 200400401404500

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are UserStory (11 properties), AcceptanceCriterion (10 properties), CreateUserStoryRequest (6 properties), UpdateUserStoryRequest (5 properties). Each schema is shown below with its type and property counts.

AcceptanceCriterion
object
A single testable condition that must be met for a user story to be accepted as complete
10 properties 2 required
CreateUserStoryRequest
object
Request body for creating a new user story
6 properties 1 required
UserStory
object
A user story representing a feature or requirement from the perspective of an end user
11 properties 3 required
UpdateUserStoryRequest
object
Request body for updating an existing user story
5 properties
UserStoryList
object
Paginated list of user stories
4 properties
ErrorResponse
object
Standard error response
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

acceptance-criteria-user-stories-api-openapi.yml Raw ↑
#User Stories
← Back to A APIs
API Details
ID
acceptance-criteria:acceptance-criteria-user-stories-api
Base URL
https://api.github.com
Docs
https://docs.github.com/en/rest/issues
Provider
Acceptance Criteria
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=acceptance-criteria-user-stories-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/acceptance-criteria-user-stories-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Acceptance Criteria User Stories API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.