ITA GROUPE / Developers

ITA GROUPE API documentation

ITA GROUPE API documentation: public company, service and portfolio endpoints, authentication, example requests, response formats and error handling.

Authentication and access

The ITA GROUPE public REST API provides read-only access to company information, services and portfolio projects. No account, API key, access token or authentication cookie is required. Responses are JSON, and public endpoints support cross-origin browser requests.

Base URL: https://www.itagroupe.com. Start with the API index or download the OpenAPI 3.1 specification.

For a tool-calling agent, use the ITA GROUPE MCP server with the same public catalog.

Make your first API request

Read a service by its published slug. This request returns its description, canonical source page and Markdown URL.

Request — read a service
curl --fail-with-body --silent --show-error 'https://www.itagroupe.com/api/services/web-app-development'
200 OK — application/json
{
  "data": {
    "slug": "web-app-development",
    "name": "Web app development",
    "description": "Web app development from ITA GROUPE: secure, scalable browser-based products designed and built by one team, from the first prototype to launch.",
    "category": "software-development",
    "categoryName": "Software Development",
    "url": "https://www.itagroupe.com/services/software-development/web-app-development",
    "markdownUrl": "https://www.itagroupe.com/services/software-development/web-app-development.md"
  }
}

Single-resource responses use { data: object }. List responses use { data: [...], total: number }.

REST endpoints

ITA GROUPE public REST API endpoints
Method and pathParametersReturns
GET /api/companyNoneCompany identity, founders, profiles and contact links.
GET /api/servicesOptional qPublished services, with an optional text filter.
GET /api/services/{slug}Service slugOne service, its description and source URLs.
GET /api/projectsOptional qPortfolio projects, with an optional text filter.
GET /api/projects/{slug}Project slugOne project, its services and case-study URL.

Choose service and project slugs from their list responses. Slugs contain lowercase letters, numbers and hyphens, with a maximum of 100 characters. Detail endpoints and the company endpoint take no query parameters. HEAD and OPTIONS are also supported.

Errors and retries

Errors use application/problem+json with type, title, status, code, detail and resolution fields. The OpenAPI document defines the complete response schemas.

  • 400: unsupported, duplicate or overlong query parameters, or an invalid detail slug.
  • 404: an unknown resource or API path.
  • 405: a write method on a read-only catalog endpoint.

Correct a 400, 404 or 405 request before retrying. GET requests do not change data and can be retried after a temporary network failure or server error with a bounded delay. Catalog reads require no idempotency key.

Use the returned source links

Service and project records include url and markdownUrl fields so agents can cite the page supporting an answer. Company records include public identity and contact links. Confirm scope, pricing, availability and delivery dates with the team. This API reads public information; it does not submit inquiries or deliver design, development or marketing work.

Connect an agent through MCP or read the agent page index.