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

Apache OFBiz Services API

List and invoke exported OFBiz services

Apache OFBiz Services API is one of 2 APIs that Apache OFBiz publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Services. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 3 JSON Schemas.

This API exposes 3 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 18.12.

Requests are made against a single base URL, https://localhost:8443/rest.

3 operations 2 paths 5 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
18.12
Base URL
https://localhost:8443/rest
Authentication
HTTP Basic, HTTP Bearer
License
Apache 2.0
Resource Areas
1

Authentication & Security 2

Apache OFBiz Services API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic Auth used only for token acquisition at /auth/token.
  • bearerAuth — JWT Bearer token obtained from /auth/token. Required for all service endpoints.

Paths & Operations 3

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

Services 3

List and invoke exported OFBiz services

GET
/services
Apache OFBiz List All Exported Services
getServices → 200401500
GET
/services/{serviceName}
Apache OFBiz Invoke Service via GET
invokeServiceGet 2 params → 200400401404500
POST
/services/{serviceName}
Apache OFBiz Invoke Service via POST
invokeServicePost 1 param body → 200400401404500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ServiceListResponse (4 properties), ServiceResponse (4 properties), ErrorResponse (3 properties), ServiceLink (3 properties). Each schema is shown below with its type and property counts.

ServiceEntry
object
A single exported OFBiz service with its metadata and invocation link.
3 properties
ServiceResponse
object
Standard API response from an OFBiz service invocation.
4 properties
ServiceLink
object
Hypermedia link to a service endpoint.
3 properties
ServiceListResponse
object
API response containing a list of exported services.
4 properties
ErrorResponse
object
Standard error response.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

apache-ofbiz-services-api-openapi.yml Raw ↑

Other APIs Apache OFBiz publishes across the network.

Apache OFBiz Authentication API
Where this information came from

This is an independent, third-party profile of Apache OFBiz Services 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.