"Not authorized to send this telegram template"

[Verate]

I'm sending telegrams that need to be marked as recruiting for an organization. I created a template but it won't let me send it. I keep getting a message saying I'm not authorized to send it.

[Atheris]

Haven't made a recruitment telegram/template in a while, but do you have an API key?

[Verate]

Haven't made a recruitment telegram/template in a while, but do you have an API key?

I have an API key for my region recruitment, but this is different. This is the kind you send manually by copy-pasting. No API involved.

[Atheris]

Haven't made a recruitment telegram/template in a while, but do you have an API key?

I have an API key for my region recruitment, but this is different. This is the kind you send manually by copy-pasting. No API involved.

Oh. Huh. I dunno, then. Do you have all the requirements for it?

[Verate]

I have an API key for my region recruitment, but this is different. This is the kind you send manually by copy-pasting. No API involved.

Oh. Huh. I dunno, then. Do you have all the requirements for it?

I should. I can still send my old regional recruitment templates just fine.

I think it might have something to do with my template being marked for an organization rather than a region. That's the only difference between the templates I'm using.

[Unibot III]

I'm sending telegrams that need to be marked as recruiting for an organization. I created a template but it won't let me send it. I keep getting a message saying I'm not authorized to send it.

This has been an ongoing problem never addressed. Over the past few years, both I and August have both reported it previously and never received any response about it??

I’m not sure the Organization template has been a functional feature for years.

[Sedgistan]

I've pinged the admins on our staff Discord channel re. this. I'm aware it's been reported previously.

[The Python]

I got the same problem too. When you attempt to use API recruitment for this, it will also give you a 403 error.

[[violet]]

Sorry, can you post a complete set of steps for me to reproduce the problem? I'm unclear on exactly who's doing what.

[The Python]

Sorry, can you post a complete set of steps for me to reproduce the problem? I'm unclear on exactly who's doing what.

First create a telegram template, works the same with API and non-API templates.
Then attempt to send it to anybody, through the API if using API template or manually if non-API

[[violet]]

Should be fixed now.

[The Python]

Should be fixed now.

Just tested, and it works! Thanks Violet!

[The Python]

Bug: It works for non-API recruitment (thanks), but I get error 403 when I want to send a non-regional recruitment telegram through API; I GHR'd because I assumed I needed a non-regional recruitment client key, but mods said that you should can use a regional recruitment key.

[[violet]]

Bug: It works for non-API recruitment (thanks), but I get error 403 when I want to send a non-regional recruitment telegram through API; I GHR'd because I assumed I needed a non-regional recruitment client key, but mods said that you should can use a regional recruitment key.

Which 403 is it? I think it will be one of these:

403 Attempt to use Region API Key for Non-Regional Recruitment
403 Region mismatch between Telegram and Client API Key

[The Python]

Bug: It works for non-API recruitment (thanks), but I get error 403 when I want to send a non-regional recruitment telegram through API; I GHR'd because I assumed I needed a non-regional recruitment client key, but mods said that you should can use a regional recruitment key.

Which 403 is it? I think it will be one of these:

403 Attempt to use Region API Key for Non-Regional Recruitment
403 Region mismatch between Telegram and Client API Key

403 Attempt to use Region API Key for Non-Regional Recruitment

[Frisbeeteria]

I GHR'd because I assumed I needed a non-regional recruitment client key, but mods said that you should can use a regional recruitment key.

More accurately, we have no process for granting keys other than regional keys. If there needs to be a process for Non-Regional Recruitment or other API use, that needs to be added to mod tools.

[The Python]

/bump because it's now on the second page

[[violet]]

Hmm okay. So originally the idea was that there would be regional API keys for regional recruiting, and you should use a non-regional API key for non-region recruiting. But if we are issuing region-based keys for everything, I will remove the check.

[The Python]

Hmm okay. So originally the idea was that there would be regional API keys for regional recruiting, and you should use a non-regional API key for non-region recruiting. But if we are issuing region-based keys for everything, I will remove the check.

It's not giving that 403 error anymore, but now it's started with a different 403 error (403 Region no longer exists.).

UPDATE: checked if it was related to the key, so I sent a regional recruitment API tg to myself, and I got 200, so it has to do with the non-regional recruitment problem

EDIT: Not a mod or anythin, but in my (admittedly unqualified) opinion, the problem could be that it checks if the region exists but because organisational has no region, maybe there needs to be something so that it doesn't do the check for organisational recruitment

[Vylixan]

Related to this, when I looked into automating sending Nations TG's about cards I want to buy from them or their puppets, I also wondered what I should then use as region to request an API-key.
Since these are not recruitment TG's at all, and are only somewhat related to a region because at the moment it concernsl The Pacific cards, and it's not guaranteed it will stay that way.
People gave the advice to just use my puppet storage region, but that seemed disingenuous somehow.
I never got further then some research into this, but what would the advised method of automating the sending of TG's be when the purpose is not recruiting for a region?

To me, this seems to be close to what The Python is doing.

[The Python]

Related to this, when I looked into automating sending Nations TG's about cards I want to buy from them or their puppets, I also wondered what I should then use as region to request an API-key.
Since these are not recruitment TG's at all, and are only somewhat related to a region because at the moment it concernsl The Pacific cards, and it's not guaranteed it will stay that way.
People gave the advice to just use my puppet storage region, but that seemed disingenuous somehow.
I never got further then some research into this, but what would the advised method of automating the sending of TG's be when the purpose is not recruiting for a region?

To me, this seems to be close to what The Python is doing.

If you're automating telegrams that recruit to an organisation (usually off-site) then you would use non-regional recruitment. Templates for these can easily be used for manual recruitment (don't know about stamps but probably will also work) but is extremely buggy if you use the API.

You can also use the API or non-API to send telegrams that aren't recruitment, it even has a lower ratelimit.

You can send non-recruitment telegrams with a regional client key, it's only buggy when you try to send non-regional recruitment.

[[violet]]

Related to this, when I looked into automating sending Nations TG's about cards I want to buy from them or their puppets, I also wondered what I should then use as region to request an API-key.
Since these are not recruitment TG's at all, and are only somewhat related to a region because at the moment it concernsl The Pacific cards, and it's not guaranteed it will stay that way.
People gave the advice to just use my puppet storage region, but that seemed disingenuous somehow.
I never got further then some research into this, but what would the advised method of automating the sending of TG's be when the purpose is not recruiting for a region?

To me, this seems to be close to what The Python is doing.

Yeah. When I created the system, the intent was that people would get a region-based API key for region recruiting, and a non-region-based API key for non-region-based recruiting. However, I understand that mods have found it simpler to require all API keys be region-based. So I think we should probably continue with that, and I will dismantle the old checks.

[The Python]

Related to this, when I looked into automating sending Nations TG's about cards I want to buy from them or their puppets, I also wondered what I should then use as region to request an API-key.
Since these are not recruitment TG's at all, and are only somewhat related to a region because at the moment it concernsl The Pacific cards, and it's not guaranteed it will stay that way.
People gave the advice to just use my puppet storage region, but that seemed disingenuous somehow.
I never got further then some research into this, but what would the advised method of automating the sending of TG's be when the purpose is not recruiting for a region?

To me, this seems to be close to what The Python is doing.

Yeah. When I created the system, the intent was that people would get a region-based API key for region recruiting, and a non-region-based API key for non-region-based recruiting. However, I understand that mods have found it simpler to require all API keys be region-based. So I think we should probably continue with that, and I will dismantle the old checks.

Hmm. I tried (again) and I'm still getting "403 Region No Longer Exists"

[The Python]

Bump?

[The Python]

Bumpity bump