fetch-hive/sdk Composer package when you want to invoke a prompt deployment from PHP. The SDK wraps the public POST /v1/prompt/invoke endpoint with an idiomatic facade, handles authentication, and exposes streaming responses as a generator of parsed event arrays.
Installation
Authentication
Set theFETCH_HIVE_API_KEY environment variable to your workspace API key (the client reads it automatically):
Basic example
Invoke a prompt deployment and read the final response:invokePrompt blocks until the prompt completes and returns the parsed JSON body as an associative array. See the non-streaming response shape.
Method reference
| Key | Type | Required | Description |
|---|---|---|---|
deployment | string | Yes | The prompt deployment name |
variant | string | No | The deployment variant name |
inputs | array | No | Key-value pairs for the prompt variables |
user | string | No | Opaque caller identifier surfaced in User Tracking |
metadata | array | No | Flat caller-defined metadata for audit and log filtering. See Invoke metadata |
streaming: false for invokePrompt. To stream, use invokePromptStream (below).
Handling the response
Streaming
UseinvokePromptStream to receive Server-Sent Events as they arrive. The method returns a Generator you can iterate with foreach:
reasoning, response, a final usage event, or an error event if the provider fails mid-stream.
Configuration
| Option | Default | Description |
|---|---|---|
api_key | FETCH_HIVE_API_KEY env var | Bearer token from the dashboard |
base_url | https://api.fetchhive.com/v1 | Override the API base URL |
timeout | 120 | Request timeout in seconds |
Errors
Non-2xx responses throwFetchHive\Sdk\Exception\ApiException carrying the status code and response body. Catch it if you need to handle failures:
Links
Next steps
- Run with API - The same flow with cURL
- Run with Python SDK
- Run with Node.js SDK
- Run with Ruby SDK
- Invoke Prompt - Full endpoint reference

