openapi: 3.2.0 info: title: Advanced Screening and Monitoring Articles API description: 'Dow Jones ### Rate limits Most endpoints are subject to a general rate limit of 10,000 requests per user per 15 minutes. Some endpoints are also subject to a global concurrent request limit of 5 simultaneous requests per customer.' version: '3' license: {} contact: {} servers: - url: API_INSTANCE security: - basicAuth: [] - jwt: [] - clientCert: [] tags: - name: Articles description: Fetch a news article by id, or stream news articles linked to an entity as JSON-L. paths: /articles/{article_id}: get: summary: Retrieve one news article by id description: 'Returns the news article for the given path value. That value may be either the article id (document id) or the original id from the article source; ### Rate Limits This endpoint is subject to a general rate limit of 10,000 requests per user per 15 minutes. ' operationId: articlesGetById tags: - Articles parameters: - name: article_id in: path required: true schema: type: string description: Article id or original id (see operation description). responses: '200': description: Success. content: application/json: schema: type: object description: News article payload returned by the Articles endpoints. required: - id - originalId - publisher - riskTags - publishedDate - title - content properties: id: type: string description: Article document id. originalId: type: string nullable: true description: Original id from the article source when available. publisher: type: string nullable: true description: Publisher or source name. riskTags: type: array description: Risk analytics labels. items: type: string publishedDate: type: string format: date-time nullable: true description: Publication time when known. title: type: string nullable: true description: Article headline when available. content: type: string nullable: true description: Full article body text. '400': description: Invalid request. content: application/json: schema: type: object required: - code - message properties: code: type: string description: Error code that can be used when contacting support or looking up information message: type: string description: Human-readable description of the error, which will usually indicate possible next steps if applicable status: type: number description: HTTP Error code examples: badInput: summary: Bad input value: code: BAD_INPUT_FORMAT message: Bad input format '401': description: Unauthenticated. content: application/json: schema: type: object required: - code - message properties: code: type: string description: Error code that can be used when contacting support or looking up information message: type: string description: Human-readable description of the error, which will usually indicate possible next steps if applicable status: type: number description: HTTP Error code '403': description: Forbidden. content: application/json: schema: type: object required: - code - message properties: code: type: string description: Error code that can be used when contacting support or looking up information message: type: string description: Human-readable description of the error, which will usually indicate possible next steps if applicable status: type: number description: HTTP Error code '404': description: Article not found or not available to this caller. content: application/json: schema: type: object required: - code - message properties: code: type: string description: Error code that can be used when contacting support or looking up information message: type: string description: Human-readable description of the error, which will usually indicate possible next steps if applicable status: type: number description: HTTP Error code examples: notFound: summary: Not found value: code: NOT_FOUND message: News article not found '500': description: Server error. content: application/json: schema: type: object required: - code - message properties: code: type: string description: Error code that can be used when contacting support or looking up information message: type: string description: Human-readable description of the error, which will usually indicate possible next steps if applicable status: type: number description: HTTP Error code examples: articleServiceError: summary: Article service error value: code: ERROR_GETTING_NEWS_ARTICLE message: An error occurred retrieving the news article /articles/entity/{entity_id}: get: summary: Stream news articles linked to an entity description: 'Streams linked news articles as JSON-L, empty body if none. ### Rate Limits This endpoint is subject to a general rate limit of 10,000 requests per user per 15 minutes. ' operationId: articlesGetByEntityId tags: - Articles parameters: - name: entity_id in: path required: true schema: type: string description: Entity id. responses: '200': description: Success. content: application/x-ndjson: schema: type: object description: News article payload returned by the Articles endpoints. required: - id - originalId - publisher - riskTags - publishedDate - title - content properties: id: type: string description: Article document id. originalId: type: string nullable: true description: Original id from the article source when available. publisher: type: string nullable: true description: Publisher or source name. riskTags: type: array description: Risk analytics labels. items: type: string publishedDate: type: string format: date-time nullable: true description: Publication time when known. title: type: string nullable: true description: Article headline when available. content: type: string nullable: true description: Full article body text. '400': description: Invalid request. content: application/json: schema: type: object required: - code - message properties: code: type: string description: Error code that can be used when contacting support or looking up information message: type: string description: Human-readable description of the error, which will usually indicate possible next steps if applicable status: type: number description: HTTP Error code examples: badInput: summary: Bad input value: code: BAD_INPUT_FORMAT message: Bad input format '401': description: Unauthenticated. content: application/json: schema: type: object required: - code - message properties: code: type: string description: Error code that can be used when contacting support or looking up information message: type: string description: Human-readable description of the error, which will usually indicate possible next steps if applicable status: type: number description: HTTP Error code '403': description: Forbidden. content: application/json: schema: type: object required: - code - message properties: code: type: string description: Error code that can be used when contacting support or looking up information message: type: string description: Human-readable description of the error, which will usually indicate possible next steps if applicable status: type: number description: HTTP Error code '404': description: Entity not found or not available to this caller. content: application/json: schema: type: object required: - code - message properties: code: type: string description: Error code that can be used when contacting support or looking up information message: type: string description: Human-readable description of the error, which will usually indicate possible next steps if applicable status: type: number description: HTTP Error code examples: notFound: summary: Not found value: code: NOT_FOUND message: Not found '500': description: Server error. content: application/json: schema: type: object required: - code - message properties: code: type: string description: Error code that can be used when contacting support or looking up information message: type: string description: Human-readable description of the error, which will usually indicate possible next steps if applicable status: type: number description: HTTP Error code examples: articleServiceError: summary: Article service error value: code: ERROR_GETTING_NEWS_ARTICLE message: An error occurred retrieving the news article components: securitySchemes: jwt: type: http scheme: bearer bearerFormat: JWT description: JWT authentication is the preferred authentication method, and should be used for new integrations. Contact support to request a service account. basicAuth: type: http scheme: basic description: Basic authentication is supported for existing users, but is deprecated. Existing users are encouraged to contact support for a dedicated service account and switch to JWT authentication.