Client access only. The Gwiksoft API is provided to clients as part of a signed service engagement. It is not a public or self-serve product; access, credentials, and usage terms are set out in your agreement. Talk to us

API Reference

Reference for the Gwiksoft API, provided to clients as part of a signed service engagement.

Base URL:https://api.gwiksoft.com/v1
Version:v1.0

Authentication

API key-based authentication with OAuth 2.0 support

Rate Limits

1,000 requests/hour for standard, unlimited for enterprise

REST Architecture

Clean, predictable REST API with JSON responses

Secure by Default

HTTPS-only with encryption at rest and in transit

Authentication

Authenticate your API requests using your API key in the Authorization header:

curl -X GET \
https://api.gwiksoft.com/v1/agents \
-H "Authorization: Bearer YOUR_API_KEY"

Keep your API keys secure. Never expose them in client-side code or public repositories.

Core Endpoints

POST/api/v1/agents
Agents

Create a new AI agent

GET/api/v1/agents/{id}
Agents

Retrieve agent details

PATCH/api/v1/agents/{id}
Agents

Update agent configuration

DELETE/api/v1/agents/{id}
Agents

Delete an agent

POST/api/v1/conversations
Conversations

Start a new conversation

GET/api/v1/conversations/{id}
Conversations

Get conversation history

POST/api/v1/orders/sync
Commerce

Sync order data

GET/api/v1/analytics
Analytics

Retrieve performance analytics

Response Format

All API responses follow a consistent JSON structure:

{
"success": true,
"data": {
// Response data
},
"meta": {
"timestamp": "2024-01-15T10:30:00Z",
"version": "1.0"
}
}

Error Codes

CodeDescription
200Success
201Resource created
400Bad request - Invalid parameters
401Unauthorized - Invalid or missing API key
403Forbidden - Insufficient permissions
404Not found
429Rate limit exceeded
500Internal server error

SDKs & Libraries

Node.js

Python

PHP

Ruby

Coming Soon

Java

Coming Soon

Go

Coming Soon

Need API Support?

Our developer support team can help with integration questions, debugging, and best practices.