[Foundry P1] Install & validate foundryvtt-rest-api on the production Foundry instance #4

Open
opened 2026-06-23 00:42:30 +00:00 by rbrooks · 0 comments
Owner

Do this first, before any adapter code. The REST module is documented as version-sensitive, so confirm it works on the actual target instance before sinking adapter time.

Scope

  • Install and configure the ThreeHats/foundryvtt-rest-api module on the production Foundry instance.
  • Set up the API key on the Foundry side.
  • Document, in docs/, the required module version, API key setup steps, and the Foundry core version the integration is tested against.

Notes

  • The module has historically been sensitive to Foundry core upgrades. Record the tested module + core version pair and flag compatibility as a maintenance concern whenever either is updated.
  • Foundry is often hosted locally or behind a VPN - validate against the real instance, not a throwaway.

Done when

  • Module installed on prod Foundry, reachable from the backend, version pair documented.

Roadmap: FoundryVTT Bidirectional Integration, Phase 1 step 1.

**Do this first**, before any adapter code. The REST module is documented as version-sensitive, so confirm it works on the actual target instance before sinking adapter time. ## Scope - Install and configure the **ThreeHats/foundryvtt-rest-api** module on the production Foundry instance. - Set up the API key on the Foundry side. - Document, in `docs/`, the required module version, API key setup steps, and the Foundry **core version** the integration is tested against. ## Notes - The module has historically been sensitive to Foundry core upgrades. Record the tested module + core version pair and flag compatibility as a maintenance concern whenever either is updated. - Foundry is often hosted locally or behind a VPN - validate against the real instance, not a throwaway. ## Done when - Module installed on prod Foundry, reachable from the backend, version pair documented. _Roadmap: FoundryVTT Bidirectional Integration, Phase 1 step 1._
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rbrooks/Quest-Board#4
No description provided.