AFAS Profit Integration

AFAS Profit exposes GetConnectors for reads and UpdateConnectors for writes, authenticated with an app connector token in the Authorization header. Portway adds that header from the environment; clients use Portway tokens.

Environment ​

The app connector token is an XML fragment, base64-encoded into the header value:

{
  "ServerName": "YOUR-SERVER",
  "Headers": {
    "Authorization": "AfasToken PHRva2VuPjx2ZXJzaW9uPjE8L3ZlcnNpb24+..."
  }
}

The environment Authorization header replaces the client's. A second environment with its own token connects the same endpoints to an AFAS test member.

Endpoints ​

{
  "Url": "https://12345.rest.afas.online/ProfitServices/connectors/Profit_Article",
  "Methods": ["GET"],
  "AllowedEnvironments": ["prod"]
}

{
  "Url": "https://12345.rest.afas.online/ProfitServices/connectors/FbSales",
  "Methods": ["POST", "PUT", "DELETE"],
  "AllowedEnvironments": ["prod"]
}

The AFAS member number replaces 12345.

Requests ​

AFAS query parameters are passed through:

GET /api/prod/Afas/Articles?skip=0&take=100&filterfieldids=ItemCode&filtervalues=A0001
Authorization: Bearer YOUR_PORTWAY_TOKEN

POST /api/prod/Afas/SalesOrders
Authorization: Bearer YOUR_PORTWAY_TOKEN
Content-Type: application/json

{
  "FbSales": {
    "Element": {
      "Fields": { "OrDa": "2026-07-23", "DbId": "10001" }
    }
  }
}

Limitations ​

• Filtering and paging use AFAS parameters (skip, take, filterfieldids, filtervalues, operatortypes), not OData.
• Fields are defined by the connector in AFAS.
• The app connector should grant only the connectors the integration uses.

Troubleshooting ​