Download the PHP package robo-meister/flow-beacon-api without Composer

On this page you can find all versions of the php package robo-meister/flow-beacon-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?

Example code of robo-meister/flow-beacon-api

Informations about the package flow-beacon-api

FlowBeacon API SDK (PHP)

Composer package: robo-meister/flow-beacon-api

This package provides the PHP helpers needed by FlowBeacon integrations that rely on Robo account access tokens and signed intent context tokens.

Trust boundaries

Account access token

An account access token authenticates the Robo account and organisation. Call verifyAccessToken() to retain the established account-token behavior.

Execution intent

An execution intent authenticates and correlates one Robo-authorized execution request. V1 minimal intent contexts remain supported by verifyIntentContext(). The additive V2 contract is verified by verifyExecutionIntent() and returns an immutable ExecutionIntentContext, rather than an unvalidated claim array.

Authentication != business eligibility. Valid execution intent != canonical outcome.

A valid signature proves only that Robo Connector issued the exact scoped execution request with the represented identity and correlation context. It does not prove FlowBeacon permission, unrelated user permissions, Risk acceptance, Quality approval, canonical AI output, or completion of business work.

Requirements

Install

Usage

For example, an inventory application can sign distinct inventory.restock.propose@2026-08-01 business and [email protected] technical identities. The structured WorkRef can identify inventory_item / item-42 without exposing or resolving the item. An absent workspace remains absent; it is never inferred from the organisation.

The caller's idempotency_key is authenticated and preserved, but the SDK does not guarantee remote exactly-once execution. Replay suppression, orchestration, provider selection, retries, and fallback are FlowBeacon runtime concerns.

See the V2 execution-intent contract for the claim schema, result correlation, and responsibility boundaries.

Return-to validation

isReturnToAllowed() compares the full origin (scheme://host[:port]) of the requested return URL against the allow-list. Paths and query strings are ignored after the origin match succeeds.

Development

Install dependencies and run the package checks from this directory:

Packagist release checklist

  1. Ensure composer validate --strict passes.
  2. Tag a semantic version, for example v0.1.0.
  3. Submit the repository or subtree split URL to Packagist with package name robo-meister/flow-beacon-api.
  4. Confirm Packagist reads this directory's composer.json and that the package page lists the expected autoload namespace.

All versions of flow-beacon-api with dependencies

PHP Build Version
Package Version
Requires php Version >=8.2
ext-json Version *
firebase/php-jwt Version ^7.0
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/flow-beacon-api contains the following files

Loading the files please wait ...