# Fillable Broker Checklist

This template can be copied directly as Markdown and filled in internally.

> Tip: You can add a short status behind each checkbox if needed, e.g. `([Owner], [Date], [Comment])`.

## Basic Information

- [ ] Broker name:
- [ ] Technical contact (name, email, Teams/Slack):
- [ ] Integration scenario defined (`A = existing API`, `B = new API`):

## Branding & Assets

- [ ] Logo provided as SVG (or alternative format)
- [ ] Logo variant for light backgrounds available
- [ ] Logo variant for dark backgrounds available (if applicable)
- [ ] Long logo version available (wordmark + icon)
- [ ] Square version/icon available

## Technical Resources

### Scenario A (existing API)

- [ ] OpenAPI/Swagger file shared
- [ ] Postman collection or equivalent API documentation shared
- [ ] Auth details documented (auth URL, token endpoint, client setup)

### Scenario B (new API)

- [ ] Implementation scope aligned with [API reference](/guides/broker-integration/api/login)
- [ ] Planned deviations documented

## Configuration Data

- [ ] Supported order models documented (e.g. limit, stop, trailing stop)
- [ ] Supported validity types documented (e.g. GFD, GTC)
- [ ] Exchange map provided (IDs, codes, display names)
- [ ] Compliance/risk warnings provided
- [ ] Custody location logic documented (IDs/codes incl. readable labels)

## API Mapping & Feature Support

### Authentication & Approvals

- [ ] Session TAN behavior described
- [ ] Alternative approval methods documented

### Data Retrieval & Performance

- [ ] Pagination for large lists clarified
- [ ] Date filters available and documented
- [ ] Historical depth of order history clarified
- [ ] API specifics/constraints documented (e.g. no parallel requests, strict rate limits, sequential processing)

### Order Functionality

- [ ] Supported order types listed
- [ ] `ChangeOrder` behavior / cancel+recreate clarified
- [ ] Supported `validityTypes` documented
- [ ] Partial executions incl. data source/endpoint documented
- [ ] Fractional trading incl. limitations documented

### Data Formats & Standards

- [ ] Timestamp format documented (preferably ISO 8601 in UTC)
- [ ] Currencies per ISO 4217 clarified
- [ ] Number formats without float rounding issues clarified

### Error Handling

- [ ] HTTP status code usage aligned (`400`/`401`/`422`, etc.)
- [ ] Error response structure documented
- [ ] Availability of translated error messages clarified
- [ ] Error code list with text proposals provided (if needed)

### Advanced Features

- [ ] Support for special assets (e.g. crypto) clarified
- [ ] Fees/tax information in order data clarified

## Test Access

- [ ] Sandbox access provided
- [ ] At least one test account provided
- [ ] Test account: standard scenario with holdings/cash available
- [ ] Test account: foreign currency scenario available
- [ ] Test account: special/compliance scenario available

## Finalization

- [ ] Open items marked and prioritized
- [ ] Next alignment meeting scheduled
- [ ] Alignment with [technical minimum requirements](/broker-integration/requirements) completed