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

Amika Repositories API

The Repositories API from Amika — 5 operation(s) for repositories.

Amika Repositories API is one of 12 APIs that Amika publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Repositories. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 9 operations across 5 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 0beta1.

Requests are made against a single base URL, https://app.amika.dev/api/v0beta1.

9 operations 5 paths 7 schemas 2 DELETE4 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0beta1
Base URL
https://app.amika.dev/api/v0beta1
Resource Areas
1

Paths & Operations 9

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

Repositories 9
GET
/repositories
List the org's repositories
→ 200401403
POST
/repositories
Create or update a repository
body → 201400401403
GET
/repositories/{id}
Read a single repository
1 param → 200401403404
DELETE
/repositories/{id}/image
Clear repository image config
1 param → 204401403404
GET
/repositories/{id}/integrations
List a repository's MCP integrations
1 param → 200401403
PUT
/repositories/{id}/integrations
Replace a repository's MCP integrations
1 param body → 200400401403404
GET
/repositories/{id}/workflow
Read a repository's workflow
1 param → 200401403404
PUT
/repositories/{id}/workflow
Replace a repository's workflow
1 param body → 200400401403404
DELETE
/repositories/{id}/workflow
Clear a repository's workflow
1 param → 204401403404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Repository (11 properties), CreateRepositoryRequest (6 properties), UpsertWorkflowRequest (3 properties), UpsertIntegrationsRequest (1 property). Each schema is shown below with its type and property counts.

UpsertWorkflowRequest
object
3 properties 2 required
ListRepositoriesResponse
array
WorkflowResponse
object
1 property 1 required
UpsertIntegrationsRequest
object
1 property 1 required
CreateRepositoryRequest
object
6 properties 1 required
RepoIntegrationsResponse
array
Repository
object
11 properties 11 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

amika-repositories-api-openapi.yml Raw ↑

Other APIs Amika publishes across the network.

Amika API keys API
Amika Docker registries API
Amika Downloads API
Amika Git user settings API
Amika Integrations API
Amika Sandboxes API
Amika SandboxSnapshots API
Amika Secrets API
Amika Services API
Amika Slack API
Amika Uploads API
Where this information came from

This is an independent, third-party profile of Amika Repositories 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.