Example papi file, On A Windows PC

Having the same issue –

Why did the plugin do away with simply entering the values?

• This reply was modified 3 years, 3 months ago by ultravibe.

Should point out I entered the values as shown in the README.md in the Apple News API-CLI, but the plugin wouldn’t accept it as valid.

`#XXXXXXX
endpoint: https://news-api.apple.com
channel_id: XXXXXXX
key: XXXXXXX
secret: XXXXXXXXXXX

I believe it is taking the values if you create a simple text file and use the above format – but there’s no notification within the plugin that it has been kind of accepted… However, using the above format, saving as XXX.papi, then going to sections, the plugin is pulling in the sections properly.

I released version 2.2.2 of the plugin on Friday, which includes a success message if the channel ID, key, and secret were successfully saved.

You are correct about the format, which can be found in the README in the CLI.

The CLI was written to work with Ruby, which theoretically will work on Windows also. At a minimum, you can download the tool and read the README on how to create the .papi file in order to upload it or paste the contents in to configure the plugin. If you are able to successfully pull a list of sections in Apple News > Sections, then you know Apple accepted the credentials.

This is what worked for me – #Website endpoint: https://news-api.apple.com channel_id: xxxxxx key: xxxxx secret: xxxxxx

Thanks, @cm3solutions – I think the line breaks got eaten by the editor, but yes, that is the correct format. At an absolute minimum, it needs:

channel_id: xxxx
key: xxxx
secret: xxxx

The comment at the top and the endpoint field aren’t used by the Publish to Apple News plugin, although I believe the endpoint field is used by the CLI utility, so should be present if you’re testing it locally via CLI.