A read request can return HTTP 200 and valid JSON while showing a different workspace from the one you intended to inspect. Before adding automation, separate three checks: the request succeeded, the response has the documented shape, and a deliberately chosen resource is present.
I maintain AppStruct. The example below uses its Social API, but the test fixture works locally without an account or API key.
Reproduce the false positive locally
Save this as workspace-identity-check.mjs and run node workspace-identity-check.mjs. Both fictional responses have HTTP 200. Only one contains the expected channel.
import assert from 'node:assert/strict'; function checkChannelPage(response, expectedId) { assert.equal(response.status, 200); assert.equal(typeof expectedId, 'string'); assert.ok(expectedId.length > 0 && !expectedId.includes('{{')); assert.ok(Array.isArray(response.body.channels)); assert.ok(response.body.channels.some((channel) => channel.id === expectedId)); } // Fixture labels only; these are not real AppStruct IDs or API responses. const expectedId = 'channel_alpha'; const right = { status: 200, body: { channels: [{ id: 'channel_alpha' }] } }; const wrong = { status: 200, body: { channels: [{ id: 'channel_beta' }] } }; // A status-only smoke test passes for both fixtures. assert.equal(right.status, 200); assert.equal(wrong.status, 200); checkChannelPage(right, expectedId); assert.throws(() => checkChannelPage(wrong, expectedId)); assert.throws(() => checkChannelPage({ status: 200, body: { channels: [] } }, expectedId)); assert.throws(() => checkChannelPage({ status: 200, body: {} }, expectedId)); assert.throws(() => checkChannelPage({ ...right, status: 401 }, expectedId)); assert.throws(() => checkChannelPage(right, '')); assert.throws(() => checkChannelPage(right, '{{expected_channel_id}}')); console.log('Passed: one matching page and six rejected fixtures.'); The rejected fixtures cover a different channel, an empty page, missing channel data, an unauthorized status, an empty expectation and an unresolved placeholder. This tests the assertion logic against in-memory fixtures. It does not test a live account or server authorization.
An empty or non-matching page means the expected resource has not been confirmed in that page. It does not, by itself, prove that the key belongs to the wrong workspace. Pagination, permissions, disconnected channels or an outdated expectation can also explain the result.
Choose the expected resource before the API call
For a real check:
- Open the intended AppStruct Social workspace in the product.
- Choose a connected channel you are permitted to inspect and establish its exact ID from an authoritative view you already trust. A display name can be duplicated.
- Keep that expectation in your own private environment as
expected_channel_id. - Use a short-lived workspace key with
social:readfor this channels request. - Compare the API result with the expectation. Keep real IDs, keys and response bodies out of public examples.
Do not set the expected ID to the first channel returned by the same request you are testing. That would make the identity check agree with whichever workspace answered.
Add a separate Postman assertion
The published read-only starter contains GET requests for public metadata, channels, draft posts, one explicitly selected post and optional analytics. Import or fork it into a private workspace you control. Its shipped checks cover status and response structure; add the expectation below to your own copy when you have independently chosen a channel.
const expected = pm.environment.get('expected_channel_id'); const body = pm.response.json(); pm.test('HTTP 200', () => pm.response.to.have.status(200)); pm.test('This page contains the deliberately selected channel', () => { pm.expect(expected).to.be.a('string').and.not.empty; pm.expect(expected.includes('{{')).to.equal(false); pm.expect(body.channels).to.be.an('array'); pm.expect(body.channels.some((channel) => channel.id === expected), 'Selected channel not confirmed in this page; inspect pagination and scope') .to.equal(true); }); Postman's test-script documentation describes the Post-response tab and pm.test assertions.
The channels request initially reads one page. If your chosen channel is on a later page, follow next_cursor while preserving the query. Do not increase permissions or change the expected channel merely to turn a failed assertion green. If no expected resource can be independently established, record identity as not checked.
Separate REST checks from an MCP connection
Use Postman desktop or an appropriate agent for AppStruct's server-to-server API; direct browser-Origin requests are rejected. A successful public OpenAPI request does not authenticate a workspace. These REST requests also do not test an MCP client's transport, tool discovery or draft-writing behavior.
The starter has no write, scheduling or publishing request and contains no account key or saved account response. Optional analytics needs the separate social:analytics:read scope. We checked the starter's format and declared routes against the public specification; this article does not claim a real authenticated account run.
For the collection download, setup sequence and a separate draft-review exercise, see the AppStruct Social connection guide.
A useful result is a read you can reconcile with the intended workspace. A green status or a passing fixture is only one part of that evidence.

