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
Insforge

Insforge Client API

The Client API from Insforge — 35 operation(s) for client.

Documentation Provider Profile APIs.io OpenAPI GitHub

Insforge Client API is one of 11 APIs that Insforge publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Clients. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 46 operations across 35 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.insforge.dev.

46 operations 35 paths 28 schemas 4 DELETE15 GET3 PATCH22 POST2 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.insforge.dev
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Insforge Client API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

Paths & Operations 46

Across 35 paths, the API surfaces 46 operations — 4 DELETE, 15 GET, 3 PATCH, 22 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Client 46
POST
/api/ai/chat/completiondeprecated
Generate chat completion (deprecated)
body → 200400401500
POST
/api/ai/image/generationdeprecated
Generate images (deprecated)
body → 200400401500
POST
/api/ai/embeddingsdeprecated
Generate embeddings (deprecated)
body → 200400401500
GET
/api/auth/public-config
Get public authentication configuration
→ 200
PATCH
/api/auth/profiles/current
Update current user's profile
body → 200400401
GET
/api/auth/profiles/{userId}
Get user profile by ID
1 param → 200400404
POST
/api/auth/users
Register new user
1 param body → 200400403409
POST
/api/auth/sessions
User login
1 param body → 200401403
POST
/api/auth/refresh
Refresh access token
2 params body → 200401403
POST
/api/auth/logout
Logout user
2 params → 200403
GET
/api/auth/sessions/current
Get current session
→ 200401
POST
/api/auth/email/send-verification
Send email verification (code or link based on config)
body → 202400
GET
/api/auth/email/verify-link
Verify email from browser link click
1 param → 302400
POST
/api/auth/email/verify
Verify email with code
1 param body → 200400401
POST
/api/auth/email/send-reset-password
Send password reset (code or link based on config)
body → 202400
POST
/api/auth/email/exchange-reset-password-token
Exchange reset password code for reset token
body → 200400401
GET
/api/auth/email/reset-password-link
Open password reset flow from browser link click
1 param → 302400
POST
/api/auth/email/reset-password
Reset password with token
body → 200400401
GET
/api/auth/oauth/{provider}
Initiate OAuth flow (PKCE)
3 params → 200400500
POST
/api/auth/oauth/exchange
Exchange OAuth code for tokens (PKCE)
1 param body → 200400401
GET
/api/auth/oauth/shared/callback/{state}
Shared OAuth callback handler
4 params → 302
GET
/api/auth/oauth/{provider}/callback
Provider-specific OAuth callback (GET)
4 params → 302
POST
/api/auth/oauth/{provider}/callback
Provider-specific OAuth callback (POST)
1 param body → 302
GET
/api/auth/oauth/custom/{key}
Initiate custom OAuth flow (PKCE)
3 params → 200400404
GET
/api/auth/oauth/custom/{key}/callback
Custom OAuth callback (GET)
3 params → 302
POST
/api/auth/id-token
Sign in with ID token (Google One Tap, native SDKs)
1 param body → 200400401
POST
/api/email/send-raw
Send raw HTML email
body → 200400401403500
GET
/functions/{slug}
Execute function (GET)
1 param → 200404502
POST
/functions/{slug}
Execute function (POST)
1 param body → 200404502
PUT
/functions/{slug}
Execute function (PUT)
1 param body → 200502
PATCH
/functions/{slug}
Execute function (PATCH)
1 param body → 200502
DELETE
/functions/{slug}
Execute function (DELETE)
1 param → 200502
GET
/api/health
Health check
→ 200
GET
/api/database/records/{tableName}
Query Records
6 params → 200404400
POST
/api/database/records/{tableName}
Create Records
2 params body → 201400404
PATCH
/api/database/records/{tableName}
Update Records
3 params body → 200404400
DELETE
/api/database/records/{tableName}
Delete Records
3 params → 204200
POST
/api/storage/buckets/{bucketName}/objects
Upload Object with Auto-Generated Key
1 param body → 201400404
DELETE
/api/storage/buckets/{bucketName}/objects
Delete Multiple Objects
1 param body → 200400403
POST
/api/storage/buckets/{bucketName}/upload-strategy
Get Upload Strategy (Direct or Presigned URL)
1 param body → 200404
PUT
/api/storage/buckets/{bucketName}/objects/{objectKey}
Upload Object
2 params body → 201400404
GET
/api/storage/buckets/{bucketName}/objects/{objectKey}
Download Object
2 params → 200404
DELETE
/api/storage/buckets/{bucketName}/objects/{objectKey}
Delete Object
2 params → 200404
POST
/api/storage/buckets/{bucketName}/objects/{objectKey}/confirm-upload
Confirm Presigned Upload
2 params body → 201404409
GET
/api/storage/buckets/{bucketName}/download-strategy/objects/{objectKey}
Get Download Strategy (Direct or Presigned URL)
2 params → 200404
POST
/api/storage/buckets/{bucketName}/objects/{objectKey}/download-strategydeprecated
Get Download Strategy (Deprecated — use GET on the canonical path)
2 params → 200404

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are ChatRequest (12 properties), UserResponse (8 properties), UploadStrategy (7 properties), SendRawEmailRequest (7 properties). Each schema is shown below with its type and property counts.

UrlCitationAnnotation
object
2 properties
EmbeddingsRequest
object
4 properties 2 required
TokenUsage
object
3 properties
Tool
object
2 properties 2 required
ChatRequest
object
12 properties 2 required
EmbeddingObject
object
3 properties
ErrorResponse_3
object
4 properties
OpenRouterImageMessage
object
2 properties
ChatMessage
object
4 properties 1 required
UploadStrategy
object
7 properties 4 required
ErrorResponse_5
object
4 properties 3 required
ErrorResponse_2
object
4 properties 3 required
StoredFile
object
6 properties 5 required
EmbeddingsResponse
object
3 properties
ChatCompletionResponse
object
4 properties
FunctionDefinition
object
3 properties 1 required
DownloadStrategy
object
4 properties 2 required
ErrorResponse
object
4 properties 3 required
SendEmailResponse
object
Empty object on success - extend with optional fields later if needed
ImageGenerationOptions
object
2 properties 2 required
ErrorResponse_4
object
4 properties 3 required
WebSearchPlugin
object
4 properties 1 required
FileParserPlugin
object
2 properties 1 required
ProjectAdminResponse
object
2 properties 2 required
ToolCall
object
3 properties 3 required
SendRawEmailRequest
object
7 properties 3 required
UserResponse
object
8 properties
ProfileResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

insforge-client-api-openapi.yml Raw ↑

Other APIs Insforge publishes across the network.

Insforge Admin API
AE Profile APIs.io
Insforge Channels API
AE Profile APIs.io
Insforge Configuration API
AE Profile APIs.io
Insforge Messages API
AE Profile APIs.io
Insforge Payment Webhooks API
AE Profile APIs.io
Insforge Permissions API
AE Profile APIs.io
Insforge Razorpay Payments API
AE Profile APIs.io
Insforge S3 Access Keys API
AE Profile APIs.io
Insforge S3 Protocol API
AE Profile APIs.io
Insforge Stripe Payments API
AE Profile APIs.io
#Clients
← Back to I APIs
API Details
ID
insforge:insforge-client-api
Base URL
https://api.insforge.dev
Docs
https://docs.insforge.dev/core-concepts/authentication/overview
Provider
Insforge
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=insforge-client-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/insforge-client-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 Insforge Client 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.