Venue and account requirements
Clarify the trading venue, available API features, relevant symbols and the account model. Integration availability should be confirmed for the specific environment rather than inferred from another exchange.
Access permissions
Specify the operations required by the software and the controls available at the venue. API access should be reviewed as part of the setup process. Account passwords and recovery phrases do not belong in a general project enquiry.
Market data and order state
Consider both incoming market information and the lifecycle of outgoing orders. A system must understand whether orders were accepted, rejected, filled or cancelled.
Failure behaviour
Agree what the software should do when a feed becomes stale, a connection drops or an exchange becomes unavailable. These behaviours should be testable before operational use.
Operational ownership
Document who manages configuration, monitors the system and handles changes. Establish a clear handover and review process.