Download the PHP package robo-meister/robo-connector-api without Composer

On this page you can find all versions of the php package robo-meister/robo-connector-api. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package robo-connector-api

Robo Connector SDK (PHP)

Lightweight PHP SDK for Robo Connector APIs. This package is framework-free and Packagist-friendly.

Install

Coverage snapshot (SDK vs routes vs OpenAPI)

Current repo state:

Area Route/controller availability OpenAPI (public/openapi*.yml) PHP SDK
App Store install flow ✅ ❌ ✅
Integration providers/payments ✅ ❌ ✅
Tickets/Documents/Invoices integration resources ✅ ❌ ✅
AI systems + billing portal ✅ ❌ ✅
Booking (public + private) ✅ ❌ ✅
Booking CRUD (/api/booking/bookings) ✅ ❌ ✅
Calendar meet/query ✅ ❌ ✅
Documents template/OCR review ✅ ❌ ✅
Social demo endpoints ✅ ❌ ✅
Orders + product catalogue + store refunds ✅ ❌ ✅
Payment observability endpoints ✅ ❌ ✅
WMS movement/scan/delivery module ✅ ❌ ✅
MES production-line module ✅ ❌ ✅
SCM transport/procurement/routing module ✅ ❌ ✅
CRM client registration + email-list membership ✅ ❌ ✅
Communication email queue + room invites ✅ ❌ ✅
BPM/work inbox + FlowBeacon/FlowScribe/AccordFlow ✅ ❌ ✅

If you need a non-wrapped endpoint, use request() directly and keep Idempotency-Key for write operations.

Authentication model

App Store endpoints

Use a user OAuth access token (or equivalent system token).

Integration API endpoints

Use organisation API token (and optionally X-Product-ID). Typed CRM, communication, payment, and email-list write helpers also add token and product_id into JSON bodies when the endpoint requires those fields and you did not pass explicit values.

Transport tuning (timeouts/headers)

Both SDK clients allow optional transport tuning for production hardening. Defaults include Accept: application/json and a package-level User-Agent.

App Store usage

Use AppStoreClient for package discovery/install APIs. Do not reuse ExternalServiceClient for these methods.

Standard data format selection

All PHP SDK requests can optionally ask Robo Connector data endpoints for a standard response format. The SDK normalizes and validates the format, sends the matching Accept header, and adds ?format=<format> unless you override the query parameter name with format_query.

Supported formats are json, pdf, csv, html, and xml.

Use fetchData() as the shared base for read-only data calls:

For custom or newly-added endpoints, request() accepts the same optional format controls:

Unsupported local format values throw Robo\ConnectorSdk\Exception\UnsupportedDataFormatException. If the server returns 404, 406, or 415 for a formatted data request, the SDK raises ApiException with a message that the endpoint does not exist or does not handle the requested format.

Integration usage by scenario

1) Provider discovery, clients, and payments

2) Tickets, documents, invoices, AI systems, and billing

3) Product catalogue, order lifecycle, purchases, and refunds

4) Booking/public scheduling and internal booking records

5) Calendar meets and query

Universal Input suggestions, logs, and requests

Providers that feed ecosystem-wide cards or signals can also post signed universal ingestion events:

6) Document templates and OCR review

7) Social posting

8) Payment observability and reconciliation

9) WMS, MES, and SCM module clients

The integration client exposes module clients for warehouse, manufacturing, and supply-chain workflows. These are thin wrappers over the existing Symfony routes and keep the same authentication, timeout, default-header, and idempotency behavior as ExternalServiceClient.

Wrapped module surfaces include:

11) Communication email and live-room helpers

12) BPM/work inbox and flow integrations

Error handling

HTTP 4xx/5xx responses throw Robo\ConnectorSdk\Exception\ApiException.

Notes


All versions of robo-connector-api with dependencies

PHP Build Version
Package Version
No informations.
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package robo-meister/robo-connector-api contains the following files

Loading the files please wait ...