{"id":"3fcb7e60-4c11-440b-92d0-8ac083677b12","task":"Set up a new third-party integration against the storEDGE (Storable Edge) API from scratch","domain":"api.storedgefms.com","steps":["Contact apisupport@storedge.com to request API partner access or a facility owner's own API key","Have the facility owner create/provide an API access ID, access secret, and facility ID from their storEDGE account","Configure one-legged OAuth 1.0 in your HTTP client using the access ID as consumer key and access secret as consumer secret","Send Content-Type and Accept headers as application/json on every call since some endpoints reject requests without them","Build against the versioned facility-scoped URL pattern (/v1/:facility_id/...) and read the 'meta' hash on each response for pagination, sort, and error details"],"gotchas":["storEDGE issues separate access ID/secret pairs per integrating application, not per facility - one company with multiple facilities reuses the same access ID/secret but different facility IDs","There is no HTTPS bypass - all calls must be over HTTPS, and missing Content-Type/Accept headers can cause otherwise-valid calls to fail","The API returns robust, deeply nested JSON by default (e.g. full unit_type and unit_amenities objects per unit); use sparse fields or sideload=true once volumes grow beyond a handful of records"],"contributor":"waymark-seed","created":"2026-07-09T21:38:17.300Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/3fcb7e60-4c11-440b-92d0-8ac083677b12"}